Frequently Asked Questions about Microsoft Entra PowerShell.
What is the difference between Microsoft Graph PowerShell SDK and Microsoft Entra PowerShell modules?
Microsoft Entra PowerShell is a part of our increased investment in Microsoft Graph PowerShell SDK. It brings high-quality and scenario-optimized Entra resource management to the Microsoft Graph PowerShell SDK. Still, it keeps all the benefits of Microsoft Graph PowerShell SDK for authorization, connection management, error handling, and (low-level) API coverage. As the module builds on the Microsoft Graph PowerShell SDK, it's interoperable.
Is the Microsoft Entra PowerShell module compatible with Microsoft Graph PowerShell?
Yes. You don't need to switch if you already use the Microsoft Graph PowerShell module. Both modules work together, and whether you use Entra module cmdlets or Microsoft Graph PowerShell SDK cmdlets for Entra resources is a matter of preference.
I need to migrate from the deprecated modules. Should I wait for Microsoft Entra PowerShell?
One of our goals with Microsoft Entra PowerShell is to help you migrate faster from AzureAD PowerShell. The module supports simplified migration for scripts that previously used AzureAD PowerShell, with over 98% compatibility by enabling the Enable-EntraAzureADAlias setting. However, it’s important to note that the legacy modules are now deprecated and will be retired (stop working) after March 30, 2025. We recommend that you act now to begin migrating your MSOnline and AzureAD PowerShell scripts. Both Microsoft Entra PowerShell and the Microsoft Graph PowerShell SDK use the latest Microsoft Graph APIs.
For test environments and nonproduction systems, you can migrate to Microsoft Entra PowerShell. We recommend migrating to the module for production systems only after it reaches General Availability. If you migrate scripts to Microsoft Graph PowerShell SDK now, there's no need to update them again with Microsoft Entra PowerShell. The module enhances without replacing Microsoft Graph PowerShell SDK.
Should I update Microsoft Graph PowerShell scripts to Microsoft Entra PowerShell?
No, Microsoft Entra PowerShell is part of the Microsoft Graph PowerShell, and the two modules are interoperable. You can install both modules side-by-side.
Is Microsoft Entra PowerShell a preconsented module like Azure AD or MSOnline PowerShell?
No, Microsoft Entra PowerShell permissions aren't preauthorized, and users must request the specific app permissions needed. This granularity ensures that the application has only the necessary permissions, providing granular control over resource management.
For maximum flexibility and granularity in application permissions, we recommend creating a custom application with Microsoft Entra PowerShell. By creating different applications for different uses of PowerShell in your tenant, you can have control over application permissions granted for specific scenarios. To use your own application identity with Microsoft Entra PowerShell, you can use the Connect-Entra cmdlet. For example:
Connect-Entra -ClientId 'YOUR_APP_ID'
I'm new to Microsoft Entra PowerShell; where do I start?
You can learn more about the module by reading our overview article. To learn how to install, authenticate, discover which cmdlet to use for a particular scenario, read how-to guides, and more. Our best practice guide helps you start on a secure foundation.
How can I provide feedback on the Microsoft Entra PowerShell Module?
You can provide feedback by visiting our GitHub repository issues section. Create a new issue with your feedback, suggestions, or any problems you encounter. Our team actively monitors and responds to feedback to improve the module.
How can I contribute to the Microsoft Entra PowerShell Module?
We welcome contributions from the community, whether it's through submitting bug reports, suggesting new features, or contributing scenario and example improvements. To get started, visit the repository, check out our contribution guidelines, and create a pull request with your changes.