[AzureStack] update az accounts and tools, lib folder (#14810)

* update Accounts module from master

* update dependencies and auth test

* Remove myget from Nuget.config

* fix static analysis

* Remove culture from markdown files - update online url

* Remove culture from markdown files - update the HelpGeneration File

* fix static analysis lib issue

* sync src/lib with master

Co-authored-by: Lei Jin <[email protected]>

Author: rakku-ms

.github/ISSUE_TEMPLATE/azurerm-module-bug-report.md

@@ -10,7 +10,7 @@ assignees: ''
 <!--
 
 - The AzureRM module has been replaced by the Az module; please see the following document for more information:
-    - https://docs.microsoft.com/en-us/powershell/azure/new-azureps-module-az
+    - https://docs.microsoft.com/powershell/azure/new-azureps-module-az
 - If you are able to, please migrate to the Az module and see if the issue is reproducible
     - If so, please file an issue using the Az module template
 - Please search the existing issues to see if there has been a similar issue filed

ChangeLog.md

@@ -1678,7 +1678,7 @@ to enable create Azure-SSIS IR with static public IP addresses.
   - Set-AzScheduledQueryRule
   - Update-AzScheduledQueryRule
   - Remove-AzScheduledQueryRule
-  - [More](https://docs.microsoft.com/en-us/rest/api/monitor/scheduledqueryrules) information about SQR API
+  - [More](https://docs.microsoft.com/rest/api/monitor/scheduledqueryrules) information about SQR API
   - Updated Az.Monitor.md to include cmdlets for GenV2(non classic) metric-based alert rule
 
 #### Az.Network
@@ -1731,7 +1731,7 @@ to enable create Azure-SSIS IR with static public IP addresses.
 ### Highlights since the last major release
 * General availability of `Az` module
 * For more information about the `Az` module, please visit the following: https://aka.ms/azps-announce
-* Added Location, ResourceGroup, and ResourceName completers: https://azure.microsoft.com/en-us/blog/completers-in-azure-powershell/
+* Added Location, ResourceGroup, and ResourceName completers: https://azure.microsoft.com/blog/completers-in-azure-powershell/
 * Added wildcard support to Get cmdlets for Az.Compute and Az.Network
 * Added interactive and username/password authentication for Windows PowerShell 5.1 only
 * Added support for Python 2 runbooks in Az.Automation
@@ -1835,7 +1835,7 @@ to enable create Azure-SSIS IR with static public IP addresses.
 ### Highlights since the last major release
 * General availability of `Az` module
 * For more information about the `Az` module, please visit the following: https://aka.ms/azps-announce
-* Added Location, ResourceGroup, and ResourceName completers: https://azure.microsoft.com/en-us/blog/completers-in-azure-powershell/
+* Added Location, ResourceGroup, and ResourceName completers: https://azure.microsoft.com/blog/completers-in-azure-powershell/
 * Added wildcard support to Get cmdlets for Az.Compute and Az.Network
 * Added interactive and username/password authentication for Windows PowerShell 5.1 only
 * Added support for Python 2 runbooks in Az.Automation
@@ -1892,7 +1892,7 @@ to enable create Azure-SSIS IR with static public IP addresses.
 ### Highlights since the last major release
 * General availability of `Az` module
 * For more information about the `Az` module, please visit the following: https://aka.ms/azps-announce
-* Added Location, ResourceGroup, and ResourceName completers: https://azure.microsoft.com/en-us/blog/completers-in-azure-powershell/
+* Added Location, ResourceGroup, and ResourceName completers: https://azure.microsoft.com/blog/completers-in-azure-powershell/
 * Added wildcard support to Get cmdlets for Az.Compute and Az.Network
 * Added interactive and username/password authentication for Windows PowerShell 5.1 only
 * Added support for Python 2 runbooks in Az.Automation
@@ -1949,7 +1949,7 @@ to enable create Azure-SSIS IR with static public IP addresses.
 ### Highlights since the last major release
 * General availability of `Az` module
 * For more information about the `Az` module, please visit the following: https://aka.ms/azps-announce
-* Added Location, ResourceGroup, and ResourceName completers: https://azure.microsoft.com/en-us/blog/completers-in-azure-powershell/
+* Added Location, ResourceGroup, and ResourceName completers: https://azure.microsoft.com/blog/completers-in-azure-powershell/
 * Added wildcard support to Get cmdlets for Az.Compute and Az.Network
 * Added interactive and username/password authentication for Windows PowerShell 5.1 only
 * Added support for Python 2 runbooks in Az.Automation
@@ -2004,7 +2004,7 @@ to enable create Azure-SSIS IR with static public IP addresses.
 ### Highlights since the last major release
 * General availability of `Az` module
 * For more information about the `Az` module, please visit the following: https://aka.ms/azps-announce
-* Added Location, ResourceGroup, and ResourceName completers: https://azure.microsoft.com/en-us/blog/completers-in-azure-powershell/
+* Added Location, ResourceGroup, and ResourceName completers: https://azure.microsoft.com/blog/completers-in-azure-powershell/
 * Added interactive and username/password authentication for Windows PowerShell 5.1 only
 * Added support for Python 2 runbooks in Az.Automation
 * Az.LogicApp: New cmdlets for Integration Account Assemblies and Batch Configuration
@@ -2078,7 +2078,7 @@ to enable create Azure-SSIS IR with static public IP addresses.
 ### Highlights since the last major release
 * General availability of `Az` module
 * For more information about the `Az` module, please visit the following: https://aka.ms/azps-announce
-* Added Location, ResourceGroup, and ResourceName completers: https://azure.microsoft.com/en-us/blog/completers-in-azure-powershell/
+* Added Location, ResourceGroup, and ResourceName completers: https://azure.microsoft.com/blog/completers-in-azure-powershell/
 * Added interactive and username/password authentication for Windows PowerShell 5.1 only
 * Added support for Python 2 runbooks in Az.Automation
 
@@ -2111,7 +2111,7 @@ General availability for Az.RecoveryServices module.
 ### Highlights since the last major release
 * General availability of `Az` module
 * For more information about the `Az` module, please visit the following: https://aka.ms/azps-announce
-* Added Location, ResourceGroup, and ResourceName completers: https://azure.microsoft.com/en-us/blog/completers-in-azure-powershell/
+* Added Location, ResourceGroup, and ResourceName completers: https://azure.microsoft.com/blog/completers-in-azure-powershell/
 * Added interactive and username/password authentication for Windows PowerShell 5.1 only
 * Added support for Python 2 runbooks in Az.Automation
 
@@ -2129,7 +2129,7 @@ General availability for Az.RecoveryServices module.
 ### Highlights since the last major release
 * General availability of `Az` module
 * For more information about the `Az` module, please visit the following: https://aka.ms/azps-announce
-* Added Location, ResourceGroup, and ResourceName completers: https://azure.microsoft.com/en-us/blog/completers-in-azure-powershell/
+* Added Location, ResourceGroup, and ResourceName completers: https://azure.microsoft.com/blog/completers-in-azure-powershell/
 * Added interactive and username/password authentication for Windows PowerShell 5.1 only
 * Added support for Python 2 runbooks in Az.Automation
 
@@ -2215,7 +2215,7 @@ General availability for Az.RecoveryServices module.
 ### Highlights since the last major release
 * General availability of `Az` module
 * For more information about the `Az` module, please visit the following: https://aka.ms/azps-announce
-* Added Location, ResourceGroup, and ResourceName completers: https://azure.microsoft.com/en-us/blog/completers-in-azure-powershell/
+* Added Location, ResourceGroup, and ResourceName completers: https://azure.microsoft.com/blog/completers-in-azure-powershell/
 
 #### Az.Accounts
 * Add 'Local' Scope to Enable-AzureRmAlias
@@ -2277,4 +2277,4 @@ General availability for Az.RecoveryServices module.
 ### Highlights since the last major release
 * General availability of `Az` module
 * For more information about the `Az` module, please visit the following: https://aka.ms/azps-announce
-* Added Location, ResourceGroup, and ResourceName completers: https://azure.microsoft.com/en-us/blog/completers-in-azure-powershell/
+* Added Location, ResourceGroup, and ResourceName completers: https://azure.microsoft.com/blog/completers-in-azure-powershell/

README.md

@@ -135,7 +135,7 @@ For detailed instructions on using Azure PowerShell, please refer to the [gettin
 
 If you find any bugs when using the Azure PowerShell modules, please file an issue in our [GitHub issues][GitHubIssues] page. Please fill out the provided template with the appropriate information.
 
-Alternatively, be sure to check out the [Azure Community Support](https://azure.microsoft.com/en-us/support/community/) if you have issues with the cmdlets or Azure services.
+Alternatively, be sure to check out the [Azure Community Support](https://azure.microsoft.com/support/community/) if you have issues with the cmdlets or Azure services.
 
 ### Feedback
 
@@ -183,15 +183,15 @@ _This project has adopted the [Microsoft Open Source Code of Conduct][CodeOfCond
 [OpenCodeEmail]: mailto:[email protected]
 
 <!-- Docs -->
-[MicrosoftAzureDocs]: https://docs.microsoft.com/en-us/azure/
-[PowerShellDocs]: https://docs.microsoft.com/en-us/powershell/
-
-[InstallationGuide]: https://docs.microsoft.com/en-us/powershell/azure/install-az-ps
-[GettingStartedGuide]: https://docs.microsoft.com/en-us/powershell/azure/get-started-azureps
-[PersistedCredentialsGuide]: https://docs.microsoft.com/en-us/powershell/azure/context-persistence
-
-[ConnectAzAccount]: https://docs.microsoft.com/en-us/powershell/module/az.accounts/connect-azaccount
-[GetAzContext]: https://docs.microsoft.com/en-us/powershell/module/az.accounts/get-azcontext
-[GetAzSubscription]: https://docs.microsoft.com/en-us/powershell/module/az.accounts/get-azsubscription
-[SetAzContext]: https://docs.microsoft.com/en-us/powershell/module/az.accounts/set-azcontext
-[SendFeedback]: https://docs.microsoft.com/en-us/powershell/module/az.accounts/send-feedback
+[MicrosoftAzureDocs]: https://docs.microsoft.com/azure/
+[PowerShellDocs]: https://docs.microsoft.com/powershell/
+
+[InstallationGuide]: https://docs.microsoft.com/powershell/azure/install-az-ps
+[GettingStartedGuide]: https://docs.microsoft.com/powershell/azure/get-started-azureps
+[PersistedCredentialsGuide]: https://docs.microsoft.com/powershell/azure/context-persistence
+
+[ConnectAzAccount]: https://docs.microsoft.com/powershell/module/az.accounts/connect-azaccount
+[GetAzContext]: https://docs.microsoft.com/powershell/module/az.accounts/get-azcontext
+[GetAzSubscription]: https://docs.microsoft.com/powershell/module/az.accounts/get-azsubscription
+[SetAzContext]: https://docs.microsoft.com/powershell/module/az.accounts/set-azcontext
+[SendFeedback]: https://docs.microsoft.com/powershell/module/az.accounts/send-feedback

build.proj

@@ -168,7 +168,7 @@
     <!-- Delete powershell runtime files -->
     <PropertyGroup>
       <RuntimeDllsIncludeList>Microsoft.Powershell.*.dll,System*.dll,Microsoft.VisualBasic.dll,Microsoft.CSharp.dll,Microsoft.CodeAnalysis.dll,Microsoft.CodeAnalysis.CSharp.dll</RuntimeDllsIncludeList>
-      <RuntimeDllsExcludeList>System.Security.Cryptography.ProtectedData.dll,System.Configuration.ConfigurationManager.dll,System.Runtime.CompilerServices.Unsafe.dll,System.IO.FileSystem.AccessControl.dll,System.Buffers.dll,System.Text.Encodings.Web.dll,System.CodeDom.dll,System.Management.dll</RuntimeDllsExcludeList>
+      <RuntimeDllsExcludeList>System.Security.Cryptography.ProtectedData.dll,System.Configuration.ConfigurationManager.dll,System.Runtime.CompilerServices.Unsafe.dll,System.IO.FileSystem.AccessControl.dll,System.Buffers.dll,System.Text.Encodings.Web.dll,System.CodeDom.dll,System.Management.dll,System.Text.Json.dll,System.Threading.Tasks.Extensions.dll</RuntimeDllsExcludeList>
     </PropertyGroup>
     <Exec Command="$(PowerShellCoreCommandPrefix) &quot;Get-ChildItem -Path $(RepoArtifacts)/$(Configuration) -Recurse -Include $(RuntimeDllsIncludeList) -Exclude $(RuntimeDllsExcludeList) | Where-Object {$_.FullName -notlike '*PreloadAssemblies*' -and $_.FullName -notlike '*NetCoreAssemblies*'} | Remove-Item -Force&quot;" />
     <Exec Command="$(PowerShellCoreCommandPrefix) &quot;Get-ChildItem -Path $(RepoArtifacts)/$(Configuration) -Recurse -Include 'runtimes' | Remove-Item -Recurse -Force&quot;" Condition="'$(CodeSign)' == 'true'" />

documentation/breaking-changes/breaking-changes-messages-help.md

@@ -29,5 +29,5 @@ Here is a [link to our milestones](https://github.com/Azure/azure-powershell/mil
 ) is a good resource on the various types of breaking changes authors can call out in a cmdlet.
 
 ### Send us feedback
-* Generic feedback : Use the [`Send-Feedback`](https://docs.microsoft.com/en-us/powershell/module/azurerm.profile/send-feedback?view=azurermps-6.11.0) cmdlet
+* Generic feedback : Use the [`Send-Feedback`](https://docs.microsoft.com/powershell/module/azurerm.profile/send-feedback?view=azurermps-6.11.0) cmdlet
 * A bug : Report issues in the [azure-powershell repository issue list](https://github.com/Azure/azure-powershell/issues) 

documentation/development-docs/azure-powershell-developer-guide.md

@@ -46,7 +46,7 @@ The following prerequisites should be completed before contributing to the Azure
 - Install the [`platyPS` module](help-generation.md#Installing-platyPS)
 - Install the latest [**.NET Core SDK** and **.NET Framework Dev Pack 4.7.2**](https://dotnet.microsoft.com/download) or greater
 - Install [PowerShell Core](https://github.com/PowerShell/PowerShell/releases/latest)
-- Set the PowerShell [execution policy](https://technet.microsoft.com/en-us/library/ee176961.aspx) to **Unrestricted** for the following versions of PowerShell:
+- Set the PowerShell [execution policy](https://technet.microsoft.com/library/ee176961.aspx) to **Unrestricted** for the following versions of PowerShell:
   - `C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe`
   - `C:\Windows\SysWOW64\WindowsPowerShell\v1.0\powershell.exe`
   - `C:\Program Files\PowerShell\{{version}}\pwsh.exe`
@@ -237,7 +237,7 @@ For complete documentation, see [`help-generation.md`](help-generation.md) in th
 
 # Adding Tests
 
-_Note_: As mentioned in the prerequisites section, set the PowerShell [execution policy](https://technet.microsoft.com/en-us/library/ee176961.aspx) to **Unrestricted** for the following versions of PowerShell:
+_Note_: As mentioned in the prerequisites section, set the PowerShell [execution policy](https://technet.microsoft.com/library/ee176961.aspx) to **Unrestricted** for the following versions of PowerShell:
 
 - `C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe`
 - `C:\Windows\SysWOW64\WindowsPowerShell\v1.0\powershell.exe`
@@ -287,7 +287,7 @@ CI in DevOps will happens under `Debug` folder. So you need to make sure that th
 
 > **Important!**
 > 1. Be sure that you have set the `ExecutionPolicy` to `Unrestricted` on both 32-bit and 64-bit PowerShell environments, as mentioned in the [prerequisites](#prerequisites) at the top
-> 2. When recording tests, if you are using a Prod environment, use ServicePrincipalName (SPN) and ServicePrincipalSecret. For more information on creating an SPN, click [here](https://docs.microsoft.com/en-us/azure/azure-resource-manager/resource-group-create-service-principal-portal).
+> 2. When recording tests, if you are using a Prod environment, use ServicePrincipalName (SPN) and ServicePrincipalSecret. For more information on creating an SPN, click [here](https://docs.microsoft.com/azure/azure-resource-manager/resource-group-create-service-principal-portal).
 
 ### AD Scenario Tests
 

documentation/development-docs/design-guidelines/cmdlet-best-practices.md

@@ -6,21 +6,21 @@ The following are naming conventions to keep in mind when coming up with a name
 
 #### Verb-Noun Format
 
-Cmdlet names should follow the _Verb-Noun_ format, where the verb is from the [list of approved PowerShell verbs](https://docs.microsoft.com/en-us/powershell/developer/cmdlet/approved-verbs-for-windows-powershell-commands), and the noun is a specific noun describing a resource within your service.
+Cmdlet names should follow the _Verb-Noun_ format, where the verb is from the [list of approved PowerShell verbs](https://docs.microsoft.com/powershell/developer/cmdlet/approved-verbs-for-windows-powershell-commands), and the noun is a specific noun describing a resource within your service.
 
 #### Noun Prefix
 
 For ARM cmdlets, the noun must be prefixed with `Az`.
 
 #### Pascal Case
 
-From the [_Strongly Encouraged Development Guidelines_](https://docs.microsoft.com/en-us/powershell/developer/cmdlet/strongly-encouraged-development-guidelines#use-pascal-case-for-cmdlet-names-sd02):
+From the [_Strongly Encouraged Development Guidelines_](https://docs.microsoft.com/powershell/developer/cmdlet/strongly-encouraged-development-guidelines#use-pascal-case-for-cmdlet-names-sd02):
 
 > _Use Pascal case for cmdlet names. In other words, capitalize the first letter of the verb and all terms used in the noun. For example, "Clear-ItemProperty"._
 
 #### Specific Noun and Noun Singularity
 
-From the [_Strongly Encouraged Development Guidelines_](https://docs.microsoft.com/en-us/powershell/developer/cmdlet/strongly-encouraged-development-guidelines#use-a-specific-noun-for-a-cmdlet-name-sd01):
+From the [_Strongly Encouraged Development Guidelines_](https://docs.microsoft.com/powershell/developer/cmdlet/strongly-encouraged-development-guidelines#use-a-specific-noun-for-a-cmdlet-name-sd01):
 
 > _Nouns used in cmdlet naming need to be very specific so that the user can discover your cmdlets. Prefix generic nouns such as "server" with a shortened version of the product name. For example, if a noun refers to a server that is running an instance of Microsoft SQL Server, use a noun such as "SQLServer". The combination of specific nouns and the short list of approved verbs enable the user to quickly discover and anticipate functionality while avoiding duplication among cmdlet names._
 >
@@ -56,7 +56,7 @@ For example, the `Get-AzVM` cmdlet uses the .NET SDK to retrieve objects of the
 
 In the case where your cmdlet doesn't return any output (_e.g._, deleting, starting, stopping a resource), the cmdlet should implement the `-PassThru` parameter and the `OutputType` should be set to `bool`. The `-PassThru` parameter is a `SwitchParameter` set by the user to signal that they would like to receive output from a cmdlet which does not return anything. If the `-PassThru` parameter is provided, you should return the value `true` so the user is made aware that the operation was successful. If the operation was unsuccessful, then the cmdlet should throw an exception.
 
-From the [_Strongly Encouraged Development Guidelines_](https://docs.microsoft.com/en-us/powershell/developer/cmdlet/strongly-encouraged-development-guidelines#support-the-passthru-parameter):
+From the [_Strongly Encouraged Development Guidelines_](https://docs.microsoft.com/powershell/developer/cmdlet/strongly-encouraged-development-guidelines#support-the-passthru-parameter):
 
 > _By default, many cmdlets that modify the system, such as the `Stop-Process` cmdlet, act as "sinks" for objects and do not return a result. These cmdlet should implement the `-PassThru` parameter to force the cmdlet to return an object._
 
@@ -120,7 +120,7 @@ The `-Force` parameter is reserved for special scenarios where additional confir
 
 ### `AsJob`
 
-All long running operations must implement the `-AsJob` parameter, which will allow the user to create jobs in the background. For more information about PowerShell jobs and the `-AsJob` parameter, read [this doc](https://docs.microsoft.com/en-us/powershell/azure/using-psjobs).
+All long running operations must implement the `-AsJob` parameter, which will allow the user to create jobs in the background. For more information about PowerShell jobs and the `-AsJob` parameter, read [this doc](https://docs.microsoft.com/powershell/azure/using-psjobs).
 
 To implement the `-AsJob` parameter, simply add the parameter to the end of the parameter list: