Skip to content

Commit c8eac22

Browse files
committed
Merge branch 'master' of https://github.com/MicrosoftDocs/azure-docs-pr into ds-fixespr01
2 parents 37609b3 + a56547f commit c8eac22

File tree

92 files changed

+3860
-340
lines changed

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

92 files changed

+3860
-340
lines changed

articles/azure-government/documentation-government-services-devtools.md

Lines changed: 1 addition & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -26,9 +26,7 @@ For more information, see [DevTest Labs public documentation](../lab-services/de
2626

2727
### Variations
2828
The following DevTest Labs features are not currently available in Azure Government:
29-
* [Azure Resource Manager templates to create multi-VM environments and PaaS resources within a Lab](../lab-services/devtest-lab-create-environment-from-arm.md).
30-
* Connect to an external GitHub repository to add Azure Resource Manager Templates, however [adding artifact repositories to leverage custom artifacts](../lab-services/devtest-lab-add-artifact-repo.md) is available.
31-
* Auto shutdown feature for Azure compute VMs, however, setting auto shutdown for [Labs](https://azure.microsoft.com/updates/azure-devtest-labs-auto-shutdown-notification/) and [Lab Virtual Machines](https://azure.microsoft.com/updates/azure-devtest-labs-set-auto-shutdown-for-a-single-lab-vm/) is available.
29+
* Auto shutdown feature for Azure compute VMs; however, setting auto shutdown for [Labs](https://azure.microsoft.com/updates/azure-devtest-labs-auto-shutdown-notification/) and [Lab Virtual Machines](https://azure.microsoft.com/updates/azure-devtest-labs-set-auto-shutdown-for-a-single-lab-vm/) is available.
3230

3331

3432
## Next steps

articles/azure-government/documentation-government-services-monitoringandmanagement.md

Lines changed: 0 additions & 95 deletions
Original file line numberDiff line numberDiff line change
@@ -81,12 +81,6 @@ For more information, see [Site Recovery commercial documentation](../site-recov
8181
The following Site Recovery features are not currently available in Azure Government:
8282
* Email notification
8383

84-
| Site Recovery | Classic | Resource Manager |
85-
| --- | --- | --- |
86-
| VMware/Physical  | GA | GA |
87-
| Hyper-V | GA | GA |
88-
| Site to Site | GA | GA |
89-
9084
The following URLs for Site Recovery are different in Azure Government:
9185

9286
| Azure Public | Azure Government | Notes |
@@ -101,95 +95,6 @@ Azure Monitor is generally available in Azure Government.
10195

10296
For more information, see [Monitor commercial documentation](https://docs.microsoft.com/azure/monitoring-and-diagnostics/monitoring-overview).
10397

104-
### Variations
105-
The following sections detail differences and workarounds for features of Azure Monitor in Azure Government:
106-
107-
#### Action Groups
108-
Action Groups are generally available in Azure Government with no differences from commercial Azure.
109-
110-
#### Activity Log Alerts
111-
Activity Log Alerts are generally available in Azure Government with no differences from commercial Azure.
112-
113-
#### Alerts Experience
114-
The unified alerts UI experience is available for metric and log alerts in Azure Government.
115-
116-
#### Autoscale
117-
Autoscale is generally available in Azure Government.
118-
119-
If you are using PowerShell/ARM/REST calls to specify settings, set the "Location" of the Autoscale to "USGov Virginia" or "USGov Iowa". The resource targeted by Autoscale can exist in any region. An example of the setting is below:
120-
121-
```powershell
122-
$rule1 = New-AzAutoscaleRule -MetricName "Requests" -MetricResourceId "/subscriptions/S1/resourceGroups/RG1/providers/Microsoft.Web/sites/WebSite1" -Operator GreaterThan -MetricStatistic Average -Threshold 10 -TimeGrain 00:01:00 -ScaleActionCooldown 00:05:00 -ScaleActionDirection Increase -ScaleActionScaleType ChangeCount -ScaleActionValue "1"
123-
$rule2 = New-AzAutoscaleRule -MetricName "Requests" -MetricResourceId "/subscriptions/S1/resourceGroups/RG1/providers/Microsoft.Web/sites/WebSite1" -Operator GreaterThan -MetricStatistic Average -Threshold 10 -TimeGrain 00:01:00 -ScaleActionCooldown 00:10:00 -ScaleActionDirection Increase -ScaleActionScaleType ChangeCount -ScaleActionValue "2"
124-
$profile1 = New-AzAutoscaleProfile -DefaultCapacity 2 -MaximumCapacity 10 -MinimumCapacity 2 -Rules $rule1, $rule2 -Name "MyProfile"
125-
$webhook_scale = New-AzAutoscaleWebhook -ServiceUri https://example.com?mytoken=mytokenvalue
126-
$notification1= New-AzAutoscaleNotification -CustomEmails [email protected] -SendEmailToSubscriptionAdministrator -SendEmailToSubscriptionCoAdministrators -Webhooks $webhook_scale
127-
Add-AzAutoscaleSetting -Location "USGov Virginia" -Name "MyScaleVMSSSetting" -ResourceGroup sdubeys-usgv -TargetResourceId /subscriptions/s1/resourceGroups/rg1/providers/Microsoft.Web/serverFarms/ServerFarm1 -AutoscaleProfiles $profile1 -Notifications $notification1
128-
```
129-
130-
If you are interested in implementing autoscale on your resources, use PowerShell/ARM/Rest calls to specify the settings.
131-
132-
For more information on using PowerShell, see [public documentation](https://docs.microsoft.com/azure/monitoring-and-diagnostics/insights-powershell-samples#create-and-manage-autoscale-settings).
133-
134-
#### Metrics
135-
Metrics are generally available in Azure Government. However, multi-dimensional metrics are supported only via the REST API. The ability to [show multi-dimensional metrics](../azure-monitor/platform/metrics-charts.md) is in preview in the Azure Government portal.
136-
137-
#### Metric Alerts
138-
The first generation of metrics alerts is generally available in both Azure Government and commercial Azure. The first generation is called *Alerts (Classic)*. The second generation of metric alerts (also called the [unified alerts experience](../azure-monitor/platform/alerts-overview.md)) is now also available, but with a reduced set of resource providers [compared to the public cloud](../azure-monitor/platform/alerts-metric-near-real-time.md). More will be added over time.
139-
140-
The resources currently supported in the second generation alerts experience are:
141-
- Microsoft.ApiManagement/service
142-
- Microsoft.Cache/redis
143-
- Microsoft.Compute/virtualMachines
144-
- Microsoft.DBforMySQL/servers
145-
- Microsoft.DBforPostgreSQL/servers
146-
- Microsoft.DBforMariaDB/servers
147-
- Microsoft.Devices/IotHubs
148-
- Microsoft.EventGrid/domains
149-
- Microsoft.EventGrid/topics
150-
- Microsoft.EventHub/clusters
151-
- Microsoft.EventHub/namespaces
152-
- Microsoft.Insights/components
153-
- Microsoft.Network/dnsZones
154-
- Microsoft.Network/loadBalancers
155-
- Microsoft.Network/natGateways
156-
- Microsoft.Network/privateEndpoints
157-
- Microsoft.Network/privateLinkServices
158-
- Microsoft.Network/trafficManagerProfiles
159-
- Microsoft.OperationalInsights/workspaces
160-
- Microsoft.PowerBIDedicated/capacities
161-
- Microsoft.Relay/namespaces
162-
- Microsoft.ServiceBus/namespaces
163-
- Microsoft.Sql/managedInstances
164-
- Microsoft.Sql/servers/databases
165-
- Microsoft.Sql/servers/elasticPools
166-
- Microsoft.Storage/storageAccounts
167-
- Microsoft.Storage/storageAccounts/blobServices
168-
- Microsoft.Storage/storageAccounts/fileServices
169-
- Microsoft.Storage/storageAccounts/queueServices
170-
- Microsoft.Storage/storageAccounts/tableServices
171-
- Microsoft.Web/hostingEnvironments/multiRolePools
172-
- Microsoft.Web/hostingEnvironments/workerPools
173-
- Microsoft.Web/serverfarms
174-
- Microsoft.Web/sites
175-
- Microsoft.Web/sites/slots
176-
177-
> [!NOTE]
178-
> Creating multi-resource metric alert rules on Virtual Machines is **currently not supported**. This article will be updated as soon as this functionality becomes available.
179-
180-
You can still use [classic alerts](../azure-monitor/platform/alerts-classic.overview.md) for resources not yet available in the second generation of alerts.
181-
182-
When using PowerShell/ARM/Rest calls to create metric alerts, you will need to set the "Location" of the metric alert to "USGov Virginia" or "USGov Iowa". An example of the setting is below:
183-
184-
```powershell
185-
$actionEmail = New-AzAlertRuleEmail -CustomEmail [email protected]
186-
$actionWebhook = New-AzAlertRuleWebhook -ServiceUri https://example.com?token=mytoken
187-
Add-AzMetricAlertRule -Name vmcpu_gt_1 -Location "USGov Virginia" -ResourceGroup myrg1 -TargetResourceId /subscriptions/s1/resourceGroups/myrg1/providers/Microsoft.ClassicCompute/virtualMachines/my_vm1 -MetricName "Percentage CPU" -Operator GreaterThan -Threshold 1 -WindowSize 00:05:00 -TimeAggregationOperator Average -Actions $actionEmail, $actionWebhook -Description "alert on CPU > 1%"
188-
```
189-
190-
For more information on using PowerShell, see [public documentation](../azure-monitor/platform/powershell-quickstart-samples.md).
191-
192-
19398
## Application Insights
19499

195100
This section describes the supplemental configuration that is required to use Application Insights in Azure Government. To learn more about Azure Monitor and Application Insights checkout the [full documentation](https://docs.microsoft.com/azure/azure-monitor/overview).

articles/azure-government/documentation-government-services-securityandidentity.md

Lines changed: 1 addition & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -149,7 +149,6 @@ All features covered in the above list are available in the US Government cloud
149149
The following Azure Active Directory Premium P1 features are currently not available in Azure Government:
150150

151151
- Azure Active Directory Domain Services
152-
- Cloud App Security
153152
- B2B Collaboration is available in Azure US Government tenants created after June, 2019. Over time, more tenants will get access to this functionality. See [How can I tell if B2B collaboration is available in my Azure US Government tenant?](../active-directory/b2b/current-limitations.md#how-can-i-tell-if-b2b-collaboration-is-available-in-my-azure-us-government-tenant)
154153

155154
The following features have known limitations in Azure Government:
@@ -183,4 +182,4 @@ For information about EMS suite capabilities in Azure Government, see the [Enter
183182

184183
## Next steps
185184

186-
For supplemental information and updates, subscribe to the [Microsoft Azure Government Blog.](https://devblogs.microsoft.com/azuregov)
185+
For supplemental information and updates, subscribe to the [Microsoft Azure Government Blog.](https://devblogs.microsoft.com/azuregov)

articles/azure-government/documentation-government-services-webandmobile.md

Lines changed: 0 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -60,19 +60,10 @@ those apps created in the public cloud:
6060
Some App Service features available in the public cloud are not yet available
6161
in Azure Government:
6262

63-
- Diagnose and solve problems
6463
- Deployment
6564
- Deployment Options: Only Local Git Repository and External Repository are available.
66-
- Deployment Center
67-
- Settings
68-
- Application Insights
6965
- Development Tools
70-
- Performance test
7166
- Resource explorer
72-
- PHP Debugging
73-
- Support & Troubleshooting
74-
- App Service Advisor
75-
- App Service Certificates
7667

7768

7869
### Considerations

articles/azure-monitor/insights/container-insights-hybrid-setup.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -223,7 +223,7 @@ To first identify the full resource ID of your Log Analytics workspace required
223223
az login
224224
az account set --subscription "Subscription Name"
225225
# execute deployment command to add container insights solution to the specified Log Analytics workspace
226-
az group deployment create --resource-group <resource group of log analytics workspace> --template-file ./containerSolution.json --parameters @./containerSolutionParams.json
226+
az deployment group create --resource-group <resource group of log analytics workspace> --name <deployment name> --template-file ./containerSolution.json --parameters @./containerSolutionParams.json
227227
```
228228
229229
The configuration change can take a few minutes to complete. When it's completed, a message is displayed that's similar to the following and includes the result:

articles/azure-resource-manager/templates/quickstart-create-templates-use-visual-studio-code.md

Lines changed: 6 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -136,7 +136,8 @@ There are many methods for deploying templates. Azure Cloud Shell is used in thi
136136
read location &&
137137
resourceGroupName="${projectName}rg" &&
138138
az group create --name $resourceGroupName --location "$location" &&
139-
az deployment group create --resource-group $resourceGroupName --template-file "$HOME/azuredeploy.json"
139+
az deployment group create --resource-group $resourceGroupName --template-file "$HOME/azuredeploy.json" &&
140+
echo "Press [ENTER] to continue ..."
140141
```
141142

142143
# [PowerShell](#tab/PowerShell)
@@ -148,6 +149,7 @@ There are many methods for deploying templates. Azure Cloud Shell is used in thi
148149

149150
New-AzResourceGroup -Name $resourceGroupName -Location "$location"
150151
New-AzResourceGroupDeployment -ResourceGroupName $resourceGroupName -TemplateFile "$HOME/azuredeploy.json"
152+
Write-Host "Press [ENTER] to continue ..."
151153
```
152154

153155
---
@@ -177,7 +179,8 @@ There are many methods for deploying templates. Azure Cloud Shell is used in thi
177179
read resourceGroupName &&
178180
echo "Enter the Storage Account name:" &&
179181
read storageAccountName &&
180-
az storage account show --resource-group $resourceGroupName --name $storageAccountName
182+
az storage account show --resource-group $resourceGroupName --name $storageAccountName &&
183+
echo "Press [ENTER] to continue ..."
181184
```
182185

183186
# [PowerShell](#tab/PowerShell)
@@ -186,6 +189,7 @@ There are many methods for deploying templates. Azure Cloud Shell is used in thi
186189
$resourceGroupName = Read-Host -Prompt "Enter the Resource Group name"
187190
$storageAccountName = Read-Host -Prompt "Enter the Storage Account name"
188191
Get-AzStorageAccount -ResourceGroupName $resourceGroupName -Name $storageAccountName
192+
Write-Host "Press [ENTER] to continue ..."
189193
```
190194

191195
---

articles/azure-resource-manager/templates/template-tutorial-create-multiple-instances.md

Lines changed: 4 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -119,7 +119,8 @@ To list all three storage accounts, omit the --name parameter:
119119
echo "Enter a project name that is used to generate resource group name:" &&
120120
read projectName &&
121121
resourceGroupName="${projectName}rg" &&
122-
az storage account list --resource-group $resourceGroupName
122+
az storage account list --resource-group $resourceGroupName &&
123+
echo "Press [ENTER] to continue ..."
123124
```
124125
125126
# [PowerShell](#tab/azure-powershell)
@@ -128,6 +129,7 @@ az storage account list --resource-group $resourceGroupName
128129
$projectName = Read-Host -Prompt "Enter a project name that is used to generate resource group name"
129130
$resourceGroupName = "${projectName}rg"
130131
Get-AzStorageAccount -ResourceGroupName $resourceGroupName
132+
Write-Host "Press [ENTER] to continue ..."
131133
```
132134
133135
---
@@ -140,7 +142,7 @@ When the Azure resources are no longer needed, clean up the resources you deploy
140142
141143
1. From the Azure portal, select **Resource group** from the left menu.
142144
2. Enter the resource group name in the **Filter by name** field.
143-
3. Select the resource group name. You shall see a total of six resources in the resource group.
145+
3. Select the resource group name. You shall see a total of three resources in the resource group.
144146
4. Select **Delete resource group** from the top menu.
145147
146148
## Next steps

articles/azure-resource-manager/templates/template-tutorial-create-templates-with-dependent-resources.md

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -132,6 +132,7 @@ By specifying the dependencies, Resource Manager efficiently deploys the solutio
132132
-adminPassword $adminPassword `
133133
-dnsLabelPrefix $dnsLabelPrefix `
134134
-TemplateFile "$HOME/azuredeploy.json"
135+
135136
Write-Host "Press [ENTER] to continue ..."
136137
```
137138

@@ -143,6 +144,7 @@ By specifying the dependencies, Resource Manager efficiently deploys the solutio
143144
$vmName = "SimpleWinVM"
144145

145146
Get-AzVM -Name $vmName -ResourceGroupName $resourceGroupName
147+
146148
Write-Host "Press [ENTER] to continue ..."
147149
```
148150

articles/azure-resource-manager/templates/template-tutorial-use-conditions.md

Lines changed: 7 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -154,6 +154,8 @@ New-AzResourceGroupDeployment `
154154
-storageAccountName $storageAccountName `
155155
-newOrExisting $newOrExisting `
156156
-TemplateFile "$HOME/azuredeploy.json"
157+
158+
Write-Host "Press [ENTER] to continue ..."
157159
```
158160

159161
> [!NOTE]
@@ -166,8 +168,12 @@ Try making another deployment with **newOrExisting** set to "existing" and speci
166168
When the Azure resources are no longer needed, clean up the resources you deployed by deleting the resource group. To delete the resource group, select **Try it** to open the Cloud Shell. To paste the PowerShell script, right-click the shell pane, and then select **Paste**.
167169

168170
```azurepowershell-interactive
169-
$resourceGroupName = Read-Host -Prompt "Enter the same resource group name you used in the last procedure"
171+
$projectName = Read-Host -Prompt "Enter the same project name you used in the last procedure"
172+
$resourceGroupName = "${projectName}rg"
173+
170174
Remove-AzResourceGroup -Name $resourceGroupName
175+
176+
Write-Host "Press [ENTER] to continue ..."
171177
```
172178

173179
## Next steps

articles/azure-resource-manager/templates/template-tutorial-use-key-vault.md

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -166,6 +166,8 @@ New-AzResourceGroupDeployment `
166166
-ResourceGroupName $resourceGroupName `
167167
-TemplateFile "$HOME/azuredeploy.json" `
168168
-TemplateParameterFile "$HOME/azuredeploy.parameters.json"
169+
170+
Write-Host "Press [ENTER] to continue ..."
169171
```
170172

171173
When you deploy the template, use the same resource group that you used in the key vault. This approach makes it easier for you to clean up the resources, because you need to delete only one resource group instead of two.
@@ -189,6 +191,8 @@ $projectName = Read-Host -Prompt "Enter the same project name that is used for c
189191
$resourceGroupName = "${projectName}rg"
190192
191193
Remove-AzResourceGroup -Name $resourceGroupName
194+
195+
Write-Host "Press [ENTER] to continue ..."
192196
```
193197

194198
## Next steps

0 commit comments

Comments
 (0)