Many PowerShell scripts written to automate operations in Microsoft 365 tenants fetch Azure AD users or mailboxes to process. In this article, we explain how to fetch user objects effectively by using filters to make sure that scripts process the right set of accounts or mailboxes.
It's great to be able to run Graph API requests in PowerShell scripts if everything goes right. This article describes why some common Graph API errors occur in scripts and what to do when the errors happen. Most errors are due to permissions assigned to the Azure AD apps used to run scripts and getting the basics will resolve those problems.
In this article, Sean McAvinue explains how to Microsoft Graph PowerShell SDK to Interact with Exchange Online and SharePoint Online.
For those wanting to eliminate the SMTP AUTH protocol, Microsoft has three ways to send email using Graph APIs. This article looks at how to use the Send-MgUserMail cmdlet and compares it to the Send-MgUserMessage cmdlet (covered in depth in a previous article). Our conclusion is that you'll probably end up using Send0-MgUserMail because it's easier to use.
Every month, Microsoft generates a new version of the Graph PowerShell SDK. And if you use the SDK with Azure Automation, you must update automation accounts with the new modules. That's a pain to do manually, but easy to automate with PowerShell as we explain here.
This article dives deep into using the SDK to perform common day-to-day tasks to manage users and groups through the Graph. Be on the look out for the next part of this series!
A Unified Approach to Microsoft 365 management The Microsoft Graph API has been around for some time now and Microsoft is moving more management functions (such as License Management for Azure AD Accounts) to the platform. When Microsoft transitions a function to the Graph, organizations might have to update PowerShell scripts. Getting started with the […]
Microsoft has extended the deprecation date for the Azure AD license management cmdlets to March 31, 2023. After that time, the cmdlets won't work. The strong recommendation is to replace all the old Azure AD and MSOL license management cmdlets in scripts with Microsoft Graph PowerShell SDK cmdlets or Graph API requests. You have an extra 7 months to do the job, do there's no excuse!
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.
MSOL and Azure AD license management cmdlets stop working in August 2022 when Microsoft 365 switches to a new license management platform. The Microsoft Graph PowerShell SDK includes cmdlets which can replace the older code, once you know how. The good news is that this article is packed full of practical examples of how to add, remove, and update licenses assigned to Azure AD accounts.
The Microsoft Graph operates on a least permission model, which means that developers are forced to ask for permissions for the actions they wish to perform. This is a very different approach to the way traditional PowerShell modules work, so it's an area to focus on when converting scripts which use cmdlets from the Azure AD and MSOL modules to the Microsoft Graph PowerShell SDK. In this article, we look at four ways to find out what permissions are needed to perform different actions and explain how the Graph use the permissions.
It's common to find a requirement to create new Microsoft 365 accounts with PowerShell. We're at a point of transition when the old method of using the Azure AD module will switch to the Microsoft Graph PowerShell SDK or Graph API queries. In this article, we explain how to create new accounts and assign licenses with both the Azure AD module and the Microsoft Graph PowerShell SDK.
