- 
                Notifications
    
You must be signed in to change notification settings  - Fork 4.1k
 
Update to USGovernmentActiveDirectoryEndpoint #4822
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 to USGovernmentActiveDirectoryEndpoint #4822
Conversation
| 
           @azuresdkci test this please  | 
    
| 
           @bernie-msft thanks for the PR, Bernarldo. This looks good to me, we just need to do some light validation on our side to ensure both endpoints work. As a note to myself, the URL has changed, but the old one will continue to be supported moving forward, according to this article: The Active Directory Authority for Azure Government has changed from https://login-us.microsoftonline.com to https://login.microsoftonline.us. The original URL will continue to work but all applications should be updated to the new authority URL.  | 
    
| 
           optimistic on-demand run here: https://azuresdkci.westus2.cloudapp.azure.com/job/powershell-demand/151/  | 
    
| 
           Thanks Mark, #sign-off  | 
    
| 
           Hi, I signed off on this. Was it ever merged?  | 
    
| 
           @bernie-msft I was able to log-in and run a few cmdlets in the   | 
    
| 
           @bernie-msft before we merge this, our team is discussing how we want to do versioning around this change (since it touches common code used by all of the modules we ship). Once we figure that out, we will merge this.  | 
    
| 
           @bernie-msft our upcoming release is next Friday (12/8), so it will be available then  | 
    
Description
Updated the USGovernmentActiveDirectoryEndpoint from login-us.microsoftonline.com to login.microsoftonline.us in AzureEnvironmentConstants.
This checklist is used to make sure that common guidelines for a pull request are followed. You can find a more complete discussion of PowerShell cmdlet best practices here.
General Guidelines
Testing Guidelines
Cmdlet Signature Guidelines
ShouldProcessand haveSupportShouldProcess=truespecified in the cmdlet attribute. You can find more information onShouldProcesshere.OutputTypeattribute if any output is produced - if the cmdlet produces no output, it should implement aPassThruparameter.Cmdlet Parameter Guidelines