HANDS ON SharePoint
HANDS ON Teams
HANDS ON Lists
HANDS ON tek
M365 Admin
Microsoft Teams: Bots in GCC-High
GCC-High customers will be able to build and deploy bots in their Microsoft Teams environment. This release supports custom, line-of-business bots.
Notifications
GCC-High customers will be able to build and deploy bots in their Microsoft Teams environment. This release supports custom, line-of-business bots.
Update the Azure AD and Microsoft 365 login experience with new Company Branding capabilities. You can apply your company’s brand guidance to authentication experiences with pre-defined templates.
With this change we are giving the ability to password protects items they download from quarantine. We want users to be confident that the items they are downloading to their systems will not execute involuntarily without their consent, and this capability will allow them to safely transport the items to external analysis tools.
More info: https://techcommunity.microsoft.com/t5/microsoft-defender-for-office/simplifying-the-quarantine-experience-part-two/ba-p/3354687
Stream (Classic) is transitioning to Stream (on SharePoint). Until Stream (Classic) fully retires, you can decide which Stream experience is most appropriate for your users on Office.com. Do this by configuring the target destination of the existing Stream tile in the Microsoft 365 app launcher from the SharePoint Admin Center.
This message is associated with Microsoft 365 Roadmap ID 88823
We are expanding coverage of the malicious URL click alert. The alert will now include any clicks in the past 48 hours (for emails) from the time the malicious URL verdict is identified.
More info: https://docs.microsoft.com/en-us/microsoft-365/compliance/alert-policies?view=o365-worldwide#default-alert-policies
We’re adding capabilities within preset security policies (Strict and Standard) to configure custom users and custom domains for impersonation protection. Additionally, within the preset security policy, you will also be able to apply the policy to all recipients instead of selected users, groups, and domains. You will still be able to exclude selected recipients.
More info: https://techcommunity.microsoft.com/t5/microsoft-defender-for-office/configurable-impersonation-protection-and-scope-for-preset/ba-p/3294459
Export feature of Activity Explorer has limitation of 10,000 rows. Our new feature will allow users to use cmdlet and export all the rows for all the data up to 30 days.
More info: https://docs.microsoft.com/en-us/microsoft-365/compliance/data-classification-activity-explorer?view=o365-worldwide
A common request from Exchange Online admins is for the ability to customize the organizations message expiration timeout. When a message can’t be delivered immediately due to a transient error, it will queue up and be periodically retried until either the message is sent or until the message expires 24 hours later. For some messages, 24 hours can be too long to wait only to find out a message wasn’t delivered. So, we’re introducing the ability for admins to customize the message expiration timeout to be less than 24 hours.
With this update, you will be able to manage the experience for each navigation item to open in a new tab.
Presenters are able to start collaborative annotation for all participants or just the presenter to annotate on shared screen content.
I've been working with Microsoft Technologies over the last ten years, mainly focused on creating collaboration and productivity solutions that drive the adoption of Microsoft Modern Workplace.
Found my content useful?
Buy Me a Beer
