IP based audio and video devices can be selected as sources in Teams Rooms making device installation and deployment easier, by avoiding long USB cable runs and use of USB extenders.
You can set up a connector in the Microsoft 365 compliance center to import physical badging data, such as employee’s raw physical access events or any physical access alarms generated by your organization’s badging system. This information can be used by the Microsoft 365 insider risk management solution to generate risk indicators that can help you identify possible malicious activity or data theft inside your organization.
More info: https://docs.microsoft.com/en-us/microsoft-365/compliance/import-physical-badging-data?view=o365-worldwide
Now unscheduled/ad hoc Teams Meetings are supported by Live Transcript.
Starting with Microsoft Edge version 92, users will have the option to upgrade navigations from HTTP to HTTPS on domains likely to support this more secure protocol. This support can also be configured to attempt delivery over HTTPS for all domains. More secure connections help protect customers from man-in-the-middle attacks
Enabling users to find any template, directly from Search – powered my ML.
Scheduling and reporting APIs will be available for integration into 3rd party applications.
You can now import, shape and refresh data from dynamic arrays in the current workbook.
Channel meetings in Teams are now supported by Live Transcript.
This feature enables
enforcing of conditional access policies during a user session. For example, if
a user attempts to download a sensitive document to an unmanaged device, they
can be prompted to satisfy an MFA challenge.
More info: https://docs.microsoft.com/en-us/cloud-app-security/release-notes
When using the SharePoint Online search APIs with app-only authentication where the app implements the Sites.Real.All permissions level or greater, the app is registered with full permissions and allowed to query across all SharePoint Online content to include user’s private OneDrive for Business content. When this change is implemented, queries using the Site.Read.All permissions level or greater will be throttled at 25 QPS.
The search query will return with a 429 response and you can simply retry the query. When waiting for 429 recovery, you should ensure to pause all search query requests you may be making to the service using similar app-only permission. Making additional calls while receiving throttle responses will extend the time it takes for your app to become unthrottled.
As we scale our system, we realize the importance of hardening the system to run it efficiently and also to protect the system and hence this change. This change is expected to rollout beginning August 2020 into the Fall of 2020.
More info: https://docs.microsoft.com/en-us/sharepoint/dev/general-development/how-to-avoid-getting-throttled-or-blocked-in-sharepoint-online
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.
HANDS ON SharePoint
HANDS ON Teams
HANDS ON Lists
HANDS ON tek
M365 Admin