-
Notifications
You must be signed in to change notification settings - Fork 387
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Update] Azure Classic service modules works with Powershell version 5.1 #2473
Comments
@SauravB-MS, there's an important message at the top of the doc stating that the Azure PowerShell Service Management module only works with Windows PowerShell: There's also a message at the very top of the doc stating that the cmdlets in this module are only for managing legacy Azure resources that use Service Management APIs: |
@SauravB-MS, Windows PowerShell version 5.1 and PowerShell version 7 are two different products (PowerShell 6 is no longer supported). There is not a Windows PowerShell version 6 or 7. Looping in @sdwheeler, the docs writer for PowerShell to clarify. |
@SauravB-MS I've submitted an update for the message on that page to help clarify for customers who aren't aware that Windows PowerShell and PowerShell are two separate products: |
@SauravB-MS Windows PowerShell is PowerShell 5.1. Windows does not ship with a newer version of PowerShell. PowerShell 6 and higher are built on .NET (core). Windows PowerShell 5.1 uses .NET Framework 4.5 or higher. |
[Enter feedback here]
Please update doc informing that the Azure Classic Module should be installed with Powershell version 5.1, not above.
Powershell version 6 and above are built on .net core and AD authentication fails with the below error, when attempting add-AzureAccount
As Cloud service IaaS is approching deprecation timeline, it's expected that this doc will be referred more to install classic module and migrate to ARM.
Document Details
⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.
The text was updated successfully, but these errors were encountered: