In this episode, the team discusses upcoming changes in M365 that will break your configuration if you don't act upon them.
Microsoft Teams Powershell Cmdlets for number management
Microsoft Teams SBC Direct Routing - Changes
Microsoft Teams Meeting recording expiration policy
IE 11 Expiration
Microsoft Exchange - Plus Addressing
Microsoft Exchange - API Retirements
Microsoft Exchange - Anti-Malware policy - Quarantine notifications for recipient
**Update**
If you have a Direct Routing as a Service (DRaaS) user with a DID for which you need to remove that DID, you must run the Remove-CsPhoneNumberAssignment cmdlet for that user and then renenable them for EnterpriseVoice using Set-CsPhoneNumberAssignment -EnterpriseVoiceEnabled $True
This enables EV without assigning a DID which would be useful for users that don't require a DID or need to be an Agent in a Call Queue for example.
In this episode, we talk to Enable UC Partners Kevin Keiller and our very own O365Eh co-host Dino Caputo about the approach and process to develop and publish a Microsoft Teams app. They have developed a Trivia application called Trivia Engine that allows participants to compete during challenges to answer the most questions correctly, as quickly as possible, for the best score. As they compete, they learn, and Trivia Engine allows you to track that learning progress.
In this Episode, a follow up to Episode 71. The teams walks through the process of running Microsoft 365 DSC in Azure Automation.
What is MicrosoftDSC?
Microsoft365DSC is an Open-Source initiative hosted on GitHub, lead by Microsoft engineers and maintained by the community. It allows you to write a definition for how your Microsoft 365 tenant should be configured, automate the deployment of that configuration, and ensures the monitoring of the defined configuration, notifying and acting on detected configuration drifts. It also allows you to extract a full-fidelity configuration out of any existing Microsoft 365 tenant. The tool covers all major Microsoft 365 workloads such as Exchange Online, Teams, Power Platforms, SharePoint and Security and Compliance.
Why automate MicrosoftDSC using a runbook?
Ordinarily, you would need to run MicrosoftDSC manually or setup an “agent” on a server to monitor changes in your tenant (tenant drift) which can be cumbersome and not always practical for some environments.
Azure Automation is a service in Azure that allows you to automate your Azure management tasks and to orchestrate actions across external systems from right within Azure.
The following guide shows you what how to setup Microsoft DSC as an Azure runbook. The runbook will monitor for changes in your Office 365 tenant an alert you when any changes do occur.
Getting everything setup in your Azure Tenant
Running MicrosoftDSC requires many prerequisite PowerShell Modules and dependencies to be installed into your Azure Tenant. This quite a cumbersome process so we have created a script to simplify this. **Shout out to fellow MVP Barbara Forbes for the inspiration for this code - https://twitter.com/Ba4bes**
M365DSCRunBookInstall
Before running this you will need to do the following things:
Microsoft365DSC is an Open-Source initiative hosted on GitHub, lead by Microsoft engineers and maintained by the community. It allows you to write a definition for how your Microsoft 365 tenant should be configured, automate the deployment of that configuration, and ensures the monitoring of the defined configuration, notifying and acting on detected configuration drifts. It also allows you to extract a full-fidelity configuration out of any existing Microsoft 365 tenant. The tool covers all major Microsoft 365 workloads such as Exchange Online, Teams, Power Platforms, SharePoint and Security and Compliance.