Added support/guidance for sovereign clouds (#554)

* update hardcoded location

* added docs

docs/wiki/Frequently-Asked-Questions.md

@@ -4,20 +4,32 @@ This article answers frequently asked questions relating to AzOps.
 
 ## In this Section
 
-  - [Subscriptions or resources not showing up in repository?](#subscriptions-or-resources-not-showing-up-in-repository)
-
-
+- [Subscriptions or resources not showing up in repository?](#subscriptions-or-resources-not-showing-up-in-repository)
+- [Deployments/push fail with deployment already exists in location error](#deployments/push-fail-with-deployment-already-exists-in-location-error)
 
 ## Subscriptions or resources not showing up in your repository?
 
 If there are invalid characters in the resource path, discovery of subscriptions, resource groups or resources will fail during push or pull operations.
 
 To confirm if this applies to you, check the pipeline logs for any of the following messages:
+
 ```powershell
-[ConvertTo-AzOpsState] The specified AzOpsState file contains invalid characters (remove any "[" or "]" characters)! <PathToResource> 
+[ConvertTo-AzOpsState] The specified AzOpsState file contains invalid characters (remove any "[" or "]" characters)! <PathToResource>
 ```
 
 ```powershell
-[New-AzOpsScope] Path not found: <PathToResource> 
+[New-AzOpsScope] Path not found: <PathToResource>
 ```
+
 Remove the invalid resource or character and retry the operation.
+
+## Deployments/push fail with deployment already exists in location error
+
+If you have changed `"Core.DefaultDeploymentRegion":` from the default `northeurope` post initial setup, subsequent Push/Deployments might fail with an error as below:
+
+`Invalid deployment location 'westeurope'. The deployment 'AzOps-microsoft.management_managementgroups-nested' already exists in location 'northeurope'`
+
+This happens because because [it is unsupported in ARM](https://docs.microsoft.com/en-us/azure/azure-resource-manager/templates/deploy-to-management-group?tabs=azure-cli#deployment-location-and-name) to create a deployment in one location when there's an existing deployment with the same name in a different location.
+
+To resolve the error, remove the failed deployment(s) from the target scope and re-run the failed Push pipeline. This can be done either under 'Deployments' at the particular scope in the Azure portal  or with [PowerShell](https://docs.microsoft.com/en-us/powershell/module/az.resources/remove-azmanagementgroupdeployment?view=azps-7.1.0)/[Azure CLI](https://docs.microsoft.com/en-us/cli/azure/deployment/mg?view=azure-cli-latest#az-deployment-mg-delete)/[REST](https://docs.microsoft.com/en-us/rest/api/resources/deployments/delete-at-management-group-scope).
+![Delete Deployments at scope](./Media/FAQ/delete_deployments.png)

docs/wiki/Roadmap.md

@@ -1,3 +1,3 @@
 ## Roadmap
 
-Up to date project tracking can be found [here](https://github.com/Azure/AzOps/projects/1)
+Up to date project tracking can be found [here](https://github.com/Azure/AzOps/projects/2)

docs/wiki/Sovereign-Clouds.md

@@ -0,0 +1,12 @@
+## Sovereign clouds
+In addition to Public Azure Cloud that most of us are familiar with, there’s also separate sovereign Azure clouds for US Government and China.
+
+To use AzOps with one of the sovereign clouds, the following additional configuration is required.
+
+1) Create the `ARM_ENVIRONMENT` variable/secret with the sovereign cloud [environment name](https://docs.microsoft.com/en-us/powershell/module/az.accounts/get-azenvironment?view=azps-7.1.0#example-1--getting-all-azure-environments) as value, for example `AzureUSGovernment` or `AzureChinaCloud`.  
+**GitHub Actions**
+![Add GH Action Secret](./Media/Actions/github_environment_secret.png)
+**Azure DevOps**
+![Add Azure DevOps variable in variable group](./Media/Pipelines/ado_environment_variable.png)
+2) Update `"Core.DefaultDeploymentRegion"` in [settings.json](https://github.com/Azure/AzOps-Accelerator/blob/main/settings.json) to a supported region in the sovereign cloud, for example `usgovvirginia` for Azure US Government and `chinaeast2`for Azure China.
+3) Run a pull to validate settings and populate the repository.

docs/wiki/_Footer.md

@@ -1,2 +1,4 @@
 **This wiki is being actively developed**  
-If you discover any documentation bugs, please raise them as an [issue](https://github.com/azure/azops/issues).
+If you discover any documentation bugs or would like to request new content, please raise them as an [issue](https://github.com/azure/azops/issues).
+
+Contributions to this wiki are done through the main repo under [docs/wiki](https://github.com/Azure/AzOps/tree/main/docs/wiki)

docs/wiki/_Sidebar.md

@@ -4,7 +4,7 @@
 
 * [Introduction](https://github.com/azure/azops/wiki/introduction)
 * [Prerequisites](https://github.com/azure/azops/wiki/prerequisites)
-
+  * [Sovereign Clouds](https://github.com/azure/azops/wiki/sovereign-clouds)
 * [Services](https://github.com/azure/azops/wiki/services)
   * [GitHub Actions](https://github.com/azure/azops/wiki/github-actions)
     * [Workload identity federation](https://github.com/azure/azops/wiki/github-oidc)
@@ -28,7 +28,7 @@
 
 ## Contributing
 
-* [Contribution-Guide](https://github.com/azure/azops/wiki/azops-contribution)
+* [Contribution Guide](https://github.com/azure/azops/wiki/azops-contribution)
 * [Releases](https://github.com/azure/azops/wiki/releases)
 * [Tests](https://github.com/azure/azops/wiki/tests)
   * [Prerelease](https://github.com/azure/azops/wiki/pre-release)

src/data/template/Microsoft.Management/managementGroups.template.jq

@@ -66,7 +66,7 @@ end
       "type": "Microsoft.Resources/deployments",
       "apiVersion": "2020-10-01",
       "name": "AzOps-microsoft.management_managementgroups-nested",
-      "location": "northeurope",
+      "location": "[deployment().location]",
       "properties": {
         "mode": "Incremental",
         "template": {