Using Managed Identities with the Microsoft Graph SDK and Teams PowerShell Modules
This article covers how to use an Azure managed identity with the Microsoft Graph PowerShell SDK and Microsoft Teams modules in an automation runbook.
This article covers how to use an Azure managed identity with the Microsoft Graph PowerShell SDK and Microsoft Teams modules in an automation runbook.
This article discusses the addition of a Group Membership report and a Mailbox Permission report to a PowerShell script aimed at helping to prepare a Tenant-to-Tenant Migration.
Microsoft 365 PowerShell is not a single entity. Rather, it spans a mixture of workload-specific modules and the Microsoft Graph PowerShell SDK. When the time comes to write a new script, what should a developer choose to use?
In this article we discuss how to create a new Microsoft 365 group using cmdlets from the Microsoft Graph PowerShell SDK. After creating the new group, we use the New-MgTeam cmdlet to team-enable the group.
Microsoft recently added the ability to set auto-reply for group mailboxes. In this article, we explain why you'd want to do such a thing and go through some PowerShell code to show how to set appropriate auto-reply messages for team-enabled Microsoft 365 Groups.
Conditional access policies grow and change as the tenant grows and changes, but not all of the old policies, groups and assignments are not always tidied up, leaving complex web of policies that target different groups or apps. To gain insights into this mess, I created a PowerShell script to document not just Conditional Access policy settings, but also detail who is impacted by each policy and why.
The complexities of Office 365 tenants only increases the complexities of creating an Office 365 migration plan. To generate an initial assessment for a tenant, I created a PowerShell script to report the most important information that influences migration planning.