Skip to content

Commit 87a366b

Browse files
authored
Merge pull request #260144 from MicrosoftDocs/main
Publish to live, Monday 4 AM PST, 12/4
2 parents b0a1417 + bbfcd06 commit 87a366b

Some content is hidden

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

42 files changed

+666
-177
lines changed

articles/ai-services/speech-service/includes/language-support/pronunciation-assessment.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -26,7 +26,7 @@ ms.author: eur
2626
|Malay (Malaysia)|`ms-MY`|
2727
|Norwegian Bokmål (Norway)|`nb-NO`|
2828
|Portuguese (Brazil)|`pt-BR`|
29-
|Russian (Russia)|`ru-RU`<sup>1</sup>|
29+
|Russian (Russia)|`ru-RU`|
3030
|Spanish (Mexico)|`es-MX` |
3131
|Spanish (Spain)|`es-ES` |
3232
|Swedish (Sweden)|`sv-SE`<sup>1</sup>|

articles/ai-services/speech-service/regions.md

Lines changed: 4 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -44,7 +44,7 @@ The following regions are supported for Speech service features such as speech t
4444
| Europe | France Central | `francecentral` |
4545
| Europe | Germany West Central | `germanywestcentral` |
4646
| Europe | Norway East | `norwayeast` |
47-
| Europe | Sweden Central | `swedentcentral` |
47+
| Europe | Sweden Central | `swedentcentral`<sup>8</sup> |
4848
| Europe | Switzerland North | `switzerlandnorth` <sup>6</sup>|
4949
| Europe | Switzerland West | `switzerlandwest` |
5050
| Europe | UK South | `uksouth` <sup>1,2,3,4,7</sup>|
@@ -70,10 +70,12 @@ The following regions are supported for Speech service features such as speech t
7070

7171
<sup>5</sup> The region supports keyword verification.
7272

73-
<sup>6</sup> The region does not support Speaker Recognition.
73+
<sup>6</sup> The region doesn't support Speaker Recognition.
7474

7575
<sup>7</sup> The region supports the [high performance](how-to-deploy-and-use-endpoint.md#add-a-deployment-endpoint) endpoint type for Custom Neural Voice.
7676

77+
<sup>8</sup> The region doesn't support Custom Neural Voice.
78+
7779
## Intent recognition
7880

7981
Available regions for intent recognition via the Speech SDK are in the following table.

articles/ai-services/speech-service/speech-services-quotas-and-limits.md

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -105,6 +105,12 @@ These limits aren't adjustable. For more information on batch synthesis latency,
105105
| Max number of simultaneous model trainings | N/A | 4 |
106106
| Max number of custom endpoints | N/A | 50 |
107107

108+
#### Real-time text to speech avatar
109+
110+
| Quota | Free (F0)| Standard (S0) |
111+
|--|--|--|
112+
| New connections per minute | Not available for F0 | 2 new connections per minute |
113+
108114
#### Audio Content Creation tool
109115

110116
| Quota | Free (F0)| Standard (S0) |
Lines changed: 94 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,94 @@
1+
---
2+
title: Perform ongoing administration for Arc-enabled System Center Virtual Machine Manager
3+
description: Learn how to perform administrator operations related to Azure Arc-enabled System Center Virtual Machine Manager
4+
ms.topic: how-to
5+
ms.date: 12/04/2023
6+
ms.service: azure-arc
7+
ms.subservice: azure-arc-scvmm
8+
author: Farha-Bano
9+
ms.author: v-farhabano
10+
manager: jsuri
11+
---
12+
13+
# Perform ongoing administration for Arc-enabled System Center Virtual Machine Manager
14+
15+
In this article, you learn how to perform various administrative operations related to Azure Arc-enabled System Center Virtual Machine Manager (SCVMM):
16+
17+
- Upgrade the Azure Arc resource bridge manually
18+
- Update the SCVMM account credentials
19+
- Collect logs from the Arc resource bridge
20+
21+
Each of these operations requires either SSH key to the resource bridge VM or the kubeconfig file that provides access to the Kubernetes cluster on the resource bridge VM.
22+
23+
## Upgrade the Arc resource bridge manually
24+
25+
Azure Arc-enabled SCVMM requires the Arc resource bridge to connect your SCVMM environment with Azure. Periodically, new images of Arc resource bridge are released to include security and feature updates. The Arc resource bridge can be manually upgraded from the SCVMM server. You must meet all upgrade [prerequisites](../resource-bridge/upgrade.md#prerequisites) before attempting to upgrade. The SCVMM server must have the kubeconfig and appliance configuration files stored locally. If the SCVMM account credentials changed after the initial deployment of the resource bridge, [update the new account credentials](administer-arc-scvmm.md#update-the-scvmm-account-credentials-using-a-new-password-or-a-new-scvmm-account-after-onboarding) before attempting manual upgrade.
26+
27+
> [!NOTE]
28+
> The manual upgrade feature is available for resource bridge version 1.0.14 and later. Resource bridges below version 1.0.14 must [perform the recovery option](./disaster-recovery.md) to upgrade to version 1.0.15 or later.
29+
30+
The manual upgrade generally takes between 30-90 minutes, depending on the network speed. The upgrade command takes your Arc resource bridge to the immediate next version, which might not be the latest available version. Multiple upgrades could be needed to reach a [supported version](../resource-bridge/upgrade.md#supported-versions). You can check your resource bridge version by checking the Azure resource of your Arc resource bridge.
31+
32+
To manually upgrade your Arc resource bridge, make sure you've installed the latest `az arcappliance` CLI extension by running the extension upgrade command from the SCVMM server:
33+
34+
```azurecli
35+
az extension add --upgrade --name arcappliance
36+
```
37+
38+
To manually upgrade your resource bridge, use the following command:
39+
40+
```azurecli
41+
az arcappliance upgrade scvmm --config-file <file path to ARBname-appliance.yaml>
42+
```
43+
44+
## Update the SCVMM account credentials (using a new password or a new SCVMM account after onboarding)
45+
46+
Azure Arc-enabled SCVMM uses the SCVMM account credentials you provided during the onboarding to communicate with your SCVMM management server. These credentials are only persisted locally on the Arc resource bridge VM.
47+
48+
As part of your security practices, you might need to rotate credentials for your SCVMM accounts. As credentials are rotated, you must also update the credentials provided to Azure Arc to ensure the functioning of Azure Arc-enabled SCVMM. You can also use the same steps in case you need to use a different SCVMM account after onboarding. You must ensure the new account also has all the [required SCVMM permissions](quickstart-connect-system-center-virtual-machine-manager-to-arc.md#prerequisites).
49+
50+
There are two different sets of credentials stored on the Arc resource bridge. You can use the same account credentials for both.
51+
52+
- **Account for Arc resource bridge**. This account is used for deploying the Arc resource bridge VM and will be used for upgrade.
53+
- **Account for SCVMM cluster extension**. This account is used to discover inventory and perform all the VM operations through Azure Arc-enabled SCVMM.
54+
55+
To update the credentials of the account for Arc resource bridge, run the following Azure CLI commands. Run the commands from a workstation that can access cluster configuration IP address of the Arc resource bridge locally:
56+
57+
```azurecli
58+
az account set -s <subscription id>
59+
az arcappliance get-credentials -n <name of the appliance> -g <resource group name>
60+
az arcappliance update-infracredentials scvmm --kubeconfig kubeconfig
61+
```
62+
For more information on the commands, see [`az arcappliance get-credentials`](/cli/azure/arcappliance#az-arcappliance-get-credentials) and [`az arcappliance update-infracredentials scvmm`](/cli/azure/arcappliance/update-infracredentials#az-arcappliance-update-infracredentials-scvmm).
63+
64+
65+
To update the credentials used by the SCVMM cluster extension on the resource bridge. This command can be run from anywhere with `connectedscvmm` CLI extension installed.
66+
67+
```azurecli
68+
az connectedscvmm scvmm connect --custom-location <name of the custom location> --location <Azure region> --name <name of the SCVMM resource in Azure> --resource-group <resource group for the SCVMM resource> --username <username for the SCVMM account> --password <password to the SCVMM account>
69+
```
70+
71+
## Collect logs from the Arc resource bridge
72+
73+
For any issues encountered with the Azure Arc resource bridge, you can collect logs for further investigation. To collect the logs, use the Azure CLI [`Az arcappliance log`](/cli/azure/arcappliance/logs#az-arcappliance-logs-scvmm) command.
74+
75+
To save the logs to a destination folder, run the following commands. These commands need connectivity to cluster configuration IP address.
76+
77+
```azurecli
78+
az account set -s <subscription id>
79+
az arcappliance get-credentials -n <name of the appliance> -g <resource group name>
80+
az arcappliance logs scvmm --kubeconfig kubeconfig --out-dir <path to specified output directory>
81+
```
82+
83+
If the Kubernetes cluster on the resource bridge isn't in functional state, you can use the following commands. These commands require connectivity to IP address of the Azure Arc resource bridge VM via SSH.
84+
85+
```azurecli
86+
az account set -s <subscription id>
87+
az arcappliance get-credentials -n <name of the appliance> -g <resource group name>
88+
az arcappliance logs scvmm --out-dir <path to specified output directory> --ip XXX.XXX.XXX.XXX
89+
```
90+
91+
## Next steps
92+
93+
- [Troubleshoot common issues related to resource bridge](../resource-bridge/troubleshoot-resource-bridge.md).
94+
- [Understand disaster recovery operations for resource bridge](./disaster-recovery.md).

articles/azure-arc/system-center-virtual-machine-manager/toc.yml

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -36,6 +36,8 @@
3636
href: install-arc-agents-using-script.md
3737
- name: Administer
3838
items:
39+
- name: Administer Arc-enabled SCVMM
40+
href: administer-arc-scvmm.md
3941
- name: Perform recovery operations for Arc resource bridge
4042
href: disaster-recovery.md
4143

articles/azure-monitor/logs/basic-logs-configure.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -181,7 +181,7 @@ All custom tables created with or migrated to the [data collection rule (DCR)-ba
181181

182182
| Service | Table |
183183
|:---|:---|
184-
| Active Directory | [AADDomainServicesDNSAuditsGeneral](/azure/azure-monitor/reference/tables/AADDomainServicesDNSAuditsGeneral)<br> [AADDomainServicesDNSAuditsDynamicUpdates](/azure/azure-monitor/reference/tables/AADDomainServicesDNSAuditsDynamicUpdates)<br>[AADServicePrincipalSignInLogs](/azure/azure-monitor/reference/tables/AADServicePrincipalSignInLogs) |
184+
| Azure Active Directory | [AADDomainServicesDNSAuditsGeneral](/azure/azure-monitor/reference/tables/AADDomainServicesDNSAuditsGeneral)<br> [AADDomainServicesDNSAuditsDynamicUpdates](/azure/azure-monitor/reference/tables/AADDomainServicesDNSAuditsDynamicUpdates)<br>[AADServicePrincipalSignInLogs](/azure/azure-monitor/reference/tables/AADServicePrincipalSignInLogs) |
185185
| API Management | [ApiManagementGatewayLogs](/azure/azure-monitor/reference/tables/ApiManagementGatewayLogs)<br>[ApiManagementWebSocketConnectionLogs](/azure/azure-monitor/reference/tables/ApiManagementWebSocketConnectionLogs) |
186186
| Application Gateways | [AGWAccessLogs](/azure/azure-monitor/reference/tables/AGWAccessLogs)<br>[AGWPerformanceLogs](/azure/azure-monitor/reference/tables/AGWPerformanceLogs)<br>[AGWFirewallLogs](/azure/azure-monitor/reference/tables/AGWFirewallLogs) |
187187
| Application Insights | [AppTraces](/azure/azure-monitor/reference/tables/apptraces) |

articles/azure-monitor/logs/log-analytics-workspace-health.md

Lines changed: 14 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ ms.topic: how-to
55
author: guywi-ms
66
ms.author: guywild
77
ms.reviewer: MeirMen
8-
ms.date: 02/07/2023
8+
ms.date: 11/23/2023
99

1010
#Customer-intent: As a Log Analytics workspace administrator, I want to know when there are latency issues in a Log Analytics workspace, so I can act to resolve the issue, contact Microsoft for support, or track that is Azure is meeting its SLA.
1111
---
@@ -26,22 +26,31 @@ Azure Service Health monitors:
2626

2727
## View Log Analytics workspace health and set up health status alerts
2828

29-
When Azure Service Health detects [average latency](../logs/data-ingestion-time.md#average-latency) in your Log Analytics workspace, the workspace resource health status is **Available**.
3029

3130
To view your Log Analytics workspace health and set up health status alerts:
3231

3332
1. Select **Resource health** from the Log Analytics workspace menu.
3433

3534
The **Resource health** screen shows:
3635

37-
- **Health history**: Indicates whether Azure Service Health has detected latency issues related to the specific Log Analytics workspace. To further investigate latency issues related to your workspace, see [Investigate latency](#investigate-log-analytics-workspace-health-issues).
36+
- **Health history**: Indicates whether Azure Service Health has detected latency or query execution issues in the specific Log Analytics workspace. To further investigate latency issues related to your workspace, see [Investigate latency](#investigate-log-analytics-workspace-health-issues).
3837
- **Azure service issues**: Displayed when a known issue with an Azure service might affect latency in the Log Analytics workspace. Select the message to view details about the service issue in Azure Service Health.
3938

4039
> [!NOTE]
4140
> - Service health notifications do not indicate that your Log Analytics workspace is necessarily affected by the know service issue. If your Log Analytics workspace resource health status is **Available**, Azure Service Health did not detect issues in your workspace.
4241
> - Resource Health excludes data types for which long ingestion latency is expected. For example, Application Insights data types that calculate the application map data and are known to add latency.
42+
4343

4444
:::image type="content" source="media/data-ingestion-time/log-analytics-workspace-latency.png" lightbox="media/data-ingestion-time/log-analytics-workspace-latency.png" alt-text="Screenshot that shows the Resource health screen for a Log Analytics workspace.":::
45+
46+
This table describes the possible resource health status values for a Log Analytics workspace:
47+
48+
| Resource health status | Description |
49+
|-|-|
50+
|Available| [Average latency](../logs/data-ingestion-time.md#average-latency) and no query execution issues detected.|
51+
|Unavailable|Higher than average latency detected.|
52+
|Degraded|Query failures detected.|
53+
|Unknown|Currently unable to determine Log Analytics workspace health because you haven't run queries or ingested data to this workspace recently.|
4554

4655
1. To set up health status alerts, you can either [enable recommended out-of-the-box alert](../alerts/alerts-overview.md#recommended-alert-rules) rules, or manually create new alert rules.
4756
- To enable the recommended alert rules:
@@ -78,7 +87,7 @@ To view Log Analytics workspace health metrics:
7887
| - | - |
7988
| Query count | Total number of user queries in the Log Analytics workspace within the selected time range.<br>This number includes only user-initiated queries, and doesn't include queries initiated by Sentinel rules and alert-related queries. |
8089
| Query failure count | Total number of failed user queries in the Log Analytics workspace within the selected time range.<br>This number includes all queries that return 5XX response codes - except 504 *Gateway Timeout* - which indicate an error related to the application gateway or the backend server.|
81-
| Query success rate | Total number of successful user queries in the Log Analytics workspace within the selected time range.<br>This number includes all queries that return 2XX, 4XX, and 504 response codes; in other words, all user queries that don't result in a service error. |
90+
| AvailabilityRate_Query | Percentage of successful user queries in the Log Analytics workspace within the selected time range.<br>This number includes all queries that return 2XX, 4XX, and 504 response codes; in other words, all user queries that don't result in a service error. |
8291

8392
## Investigate Log Analytics workspace health issues
8493

@@ -88,8 +97,7 @@ To investigate Log Analytics workspace health issues:
8897
- [Query](./queries.md) the data in your Log Analytics workspace to [understand which factors are contributing greater than expected latency in your workspace](../logs/data-ingestion-time.md).
8998
- [Use the `_LogOperation` function to view and set up alerts about operational issues](../logs/monitor-workspace.md) logged in your Log Analytics workspace.
9099

91-
92-
100+
93101

94102
## Next steps
95103

articles/azure-resource-manager/bicep/bicep-cli.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -176,7 +176,7 @@ The `publish` command adds a module to a registry. The Azure container registry
176176

177177
After publishing the file to the registry, you can [reference it in a module](modules.md#file-in-registry).
178178

179-
To use the publish command, you must have [Bicep CLI version 0.4.X or higher](./install.md). To use the `--documentationUri`/`-d` parameter, you must have [Bicep CLI version 0.14.X or higher](./install.md).
179+
To use the publish command, you must have [Bicep CLI version 0.14.X or higher](./install.md). To use the `--documentationUri`/`-d` parameter, you must have [Bicep CLI version 0.14.X or higher](./install.md).
180180

181181
To publish a module to a registry, use:
182182

0 commit comments

Comments
 (0)