Azure Automation runbooks can run Exchange Online PowerShell code on sandbox machines. Is this a good way of getting work done? In this article, we examine how to create an Azure automation account, a RunAs account, and some runbooks for PowerShell code to run against Exchange Online and other Microsoft 365 data.
Read articles and blog posts about PowerShell on Practical365.com.
With an increasing number of companies moving to Intune for endpoint management, more applications must be deployed via Intune to ensure users can access the applications they need to perform job functions. This article walks you through the steps to deploy a legacy application and guides you through converting an .exe installer into an import-ready format for Intune.
Microsoft 365 has many built-in controls to manage how users communicate externally, however, these controls do not generally extend to internal communication. While this is fine in most environments, situations exist where a degree of separation is required to segregate communication across different groups of users. This article details the configuration of Address Book Policies, and how they can be extended to include Teams.
Microsoft has updated the Teams PowerShell module to allow it to run in a Cloud Shell session. This is good news if you need to run one or two Teams cmdlets without access to your normal workstation, but it’s not so good if you expect to run code which runs well in normal PowerShell sessions. The limitations which exist get in the way of getting work done, which is a pity.
Like all the other Microsoft 365 administrative consoles, the Teams admin center doesn’t have any print options. If you want to print off any kind of information about Teams settings, you need to write your own code. PowerShell makes it easy to create a report about the Microsoft Teams policy assignments for user accounts. In this article, we explain how to extract policy information and generate a HTML report.