You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/azure-government/documentation-government-services-devtools.md
+1-3Lines changed: 1 addition & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -26,9 +26,7 @@ For more information, see [DevTest Labs public documentation](../lab-services/de
26
26
27
27
### Variations
28
28
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.
Copy file name to clipboardExpand all lines: articles/azure-government/documentation-government-services-monitoringandmanagement.md
-95Lines changed: 0 additions & 95 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -81,12 +81,6 @@ For more information, see [Site Recovery commercial documentation](../site-recov
81
81
The following Site Recovery features are not currently available in Azure Government:
82
82
* Email notification
83
83
84
-
| Site Recovery | Classic | Resource Manager |
85
-
| --- | --- | --- |
86
-
| VMware/Physical | GA | GA |
87
-
| Hyper-V | GA | GA |
88
-
| Site to Site | GA | GA |
89
-
90
84
The following URLs for Site Recovery are different in Azure Government:
91
85
92
86
| Azure Public | Azure Government | Notes |
@@ -101,95 +95,6 @@ Azure Monitor is generally available in Azure Government.
101
95
102
96
For more information, see [Monitor commercial documentation](https://docs.microsoft.com/azure/monitoring-and-diagnostics/monitoring-overview).
103
97
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:
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:
> 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:
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
-
193
98
## Application Insights
194
99
195
100
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).
Copy file name to clipboardExpand all lines: articles/azure-government/documentation-government-services-securityandidentity.md
+1-2Lines changed: 1 addition & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -149,7 +149,6 @@ All features covered in the above list are available in the US Government cloud
149
149
The following Azure Active Directory Premium P1 features are currently not available in Azure Government:
150
150
151
151
- Azure Active Directory Domain Services
152
-
- Cloud App Security
153
152
- 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)
154
153
155
154
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
183
182
184
183
## Next steps
185
184
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)
Copy file name to clipboardExpand all lines: articles/azure-monitor/insights/container-insights-hybrid-setup.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -223,7 +223,7 @@ To first identify the full resource ID of your Log Analytics workspace required
223
223
az login
224
224
az account set --subscription "Subscription Name"
225
225
# 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
227
227
```
228
228
229
229
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:
0 commit comments