Forum Discussion
AzureAD Powershell 7
gzygadlo The recommended approach, until those modules are fully compatible with newer versions of PowerShell, would be to import them with the -UseWindowsPowerShell option in your PowerShell 7 session. This will load the module in the version of PowerShell included with Windows, but using implicit remoting you can use it as if it were loaded in PowerShell 7.
This is described on this webpage.
gzygadlo The recommended approach, until those modules are fully compatible with newer versions of PowerShell, would be to import them with the -UseWindowsPowerShell option in your PowerShell 7 session. This will load the module in the version of PowerShell included with Windows, but using implicit remoting you can use it as if it were loaded in PowerShell 7.
This is described on this webpage.
pvanberlo is there any timeline when this will be fixed? (Or AZ be a 100% replacement?)
A lot has changed since this was first posted in 2021.
Nothing will likely be fixed in the AzureAD and AzureADPreview modules as they are now deprecated (having had their deprecation date postponed a few times already prior to March 2024).
The only supported pathway moving forward is - as per pvanberlo's comment above - to leverage the Microsoft Graph modules (for which there are now two flavours these days: normal and beta - with beta frequently exposing significantly more data).
Do not use AzureAD* for any new work, and for any existing work, you should already be planning how to migrate off them prior to March 2025 (at the time of writing).
Also make sure for any existing AzurAD* modules installed that they're running at least the minimum version listed in the deprecation notice above.
Cheers,
Lain
Wolfgang_Bures_SV Have you considered moving to the Microsoft Graph PowerShell modules as the recommended replacement of the Azure AD module? In general I find the Graph PS modules to be of very good quality and can be used in most circumstances.
