You are able to install the module, but you are not able to authenticate. There are some limitations to keep in mind though: PowerShell 5.1ĪzureAD is officially not supported in PowerShell 7+. You can install the module from the PowerShell gallery by usingĪfter you have installed the module, you can import it and connect to your tenantĪn Authentication windows will pop up and you can authenticate as usual. The cmdlets we are going to use are part of the AzureAD PowerShell module.
So if that is your use case, the AzureAD module is the way to go. Authentication through Connect-AzureAD is a breeze compared to the service principal approach you need for the Graph API. In my opinion, using the AzureAD module is the best way to go if you want to call these scripts interactively. If you would like to use PowerShell 7 and a Service Principal without learning the API, you could consider the DCToolbox module.
And automation running in for example Azure Functions is more clean thanks to working with a service principal. The biggest one being that it works natively in PowerShell 7+, where the AzureAD module doesn’t. So which should you choose? Practically, there are some advantages on using the Graph API. (To learn more about how, see my previous post.) You do have the option to call the API directly from PowerShell. I assume they are a wrapper around the Graph API, which also makes it possible to manage Conditional Access Policies. The cmdlets we are going to use today are part of the AzureAD module.
In my opinion, the PowerShell cmdlets aren’t all that intuitive, which is the reason I want to show in this post how to backup and restore Conditional Access Policies with PowerShell. This can give you some nice options to backup, document and restore Conditional access policies. Since the summer of 2020, the AzureAD PowerShell module provides cmdlets that can help you manage Conditional access policies.
0 kommentar(er)
