Skip to content

Commit 78ae08d

Browse files
authored
Merge pull request #260959 from MicrosoftDocs/main
Publish to live, Tuesday 4 AM PST, 12/12
2 parents 3b44399 + a843c39 commit 78ae08d

25 files changed

+260
-63
lines changed

articles/ai-services/speech-service/includes/release-notes/release-notes-tts.md

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -6,6 +6,12 @@ ms.date: 02/28/2023
66
ms.author: eur
77
---
88

9+
### December 2023 release
10+
11+
#### Custom neural voice
12+
13+
The newly trained voice models now support 48 kHz sample rate, irrespective of the model version. For previously trained voice models, it's necessary to [upgrade the engine version](../../how-to-custom-voice-create-voice.md?tabs=neural#update-engine-version-for-your-voice-model) to at least **2023.11.13.0** version to enhance the sample rate to 48 kHz.
14+
915
### November 2023 release
1016

1117
#### Personal voice

articles/aks/artifact-streaming.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -75,7 +75,7 @@ Enablement on ACR is a prerequisite for Artifact Streaming on AKS. For more info
7575
4. Push or import an image to the registry using the [`az acr import`][az-acr-import] command.
7676
7777
```azurecli-interactive
78-
az acr import -source docker.io/jupyter/all-spark-notebook:latest -t jupyter/all-spark-notebook:latest
78+
az acr import --source docker.io/jupyter/all-spark-notebook:latest -t jupyter/all-spark-notebook:latest
7979
```
8080
8181
5. Create a streaming artifact from the image using the [`az acr artifact-streaming create`][az-acr-artifact-streaming-create] command.

articles/aks/open-service-mesh-integrations.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -200,13 +200,13 @@ Before you can enable metrics on your mesh to integrate with Azure Monitor, make
200200

201201
4. Navigate to the Azure portal and select your AKS cluster.
202202
5. Under **Monitoring**, select **Logs**.
203-
6. In the **Monitoring** section, query the `InsightsMetrics` table to view metrics in the enabled namespaces. For example, the following query shows the *envoy* metrics for the *myappnamespace* namespace:
203+
6. In the **Monitoring** section, query the `InsightsMetrics` table to view metrics in the enabled namespaces. For example, the following query shows the *envoy* metrics for the *default* namespace:
204204

205205
```sh
206206
InsightsMetrics
207207
| where Name contains "envoy"
208208
| extend t=parse_json(Tags)
209-
| where t.app == "myappnamespace"
209+
| where t.namespace == "default"
210210
```
211211

212212
## Automation and developer tools

articles/automation/change-tracking/overview.md

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -10,6 +10,9 @@ ms.topic: conceptual
1010

1111
# Change Tracking and Inventory overview
1212

13+
> [!Important]
14+
> - Change Tracking and Inventory using Log Analytics agent will retire on **31 August 2023** and we recommend that you use Azure Monitoring Agent as the new supporting agent. Follow the guidelines for [migration from Change Tracking and inventory using Log Analytics to Change Tracking and inventory using Azure Monitoring Agent version](guidance-migration-log-analytics-monitoring-agent.md).
15+
1316
This article introduces you to Change Tracking and Inventory in Azure Automation. This feature tracks changes in virtual machines hosted in Azure, on-premises, and other cloud environments to help you pinpoint operational and environmental issues with software managed by the Distribution Package Manager. Items that are tracked by Change Tracking and Inventory include:
1417

1518
- Windows software

articles/automation/update-management/overview.md

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -10,7 +10,8 @@ ms.topic: conceptual
1010
# Update Management overview
1111

1212
> [!Important]
13-
> Azure Log Analytics agent, also known as the Microsoft Monitoring Agent (MMA) will be [retired in August 2024](https://azure.microsoft.com/updates/were-retiring-the-log-analytics-agent-in-azure-monitor-on-31-august-2024/). Azure Automation Update Management solution relies on this agent and may encounter issues once the agent is retired as it does not work with Azure Monitoring Agent (AMA). Therefore, if you are using the Azure Automation Update Management solution, we recommend that you move to Azure Update Manager for your software update needs. All the capabilities of Azure Automation Update management solution will be available on Azure Update Manager before the retirement date. Follow the [guidance](../../update-center/guidance-migration-automation-update-management-azure-update-manager.md) to move your machines and schedules from Automation Update Management to Azure Update Manager.
13+
> - Azure Automation Update Management will retire on **31 August 2023**. Follow the guidelines for [migration to Azure Update Manager](../../update-manager/guidance-migration-automation-update-management-azure-update-manager.md).
14+
> - Azure Log Analytics agent, also known as the Microsoft Monitoring Agent (MMA) will be [retired in August 2024](https://azure.microsoft.com/updates/were-retiring-the-log-analytics-agent-in-azure-monitor-on-31-august-2024/). Azure Automation Update Management solution relies on this agent and may encounter issues once the agent is retired as it does not work with Azure Monitoring Agent (AMA). Therefore, if you are using the Azure Automation Update Management solution, we recommend that you move to Azure Update Manager for your software update needs. All the capabilities of Azure Automation Update management solution will be available on Azure Update Manager before the retirement date. Follow the [guidance](../../update-center/guidance-migration-automation-update-management-azure-update-manager.md) to move your machines and schedules from Automation Update Management to Azure Update Manager.
1415
1516
You can use Update Management in Azure Automation to manage operating system updates for your Windows and Linux virtual machines in Azure, physical or VMs in on-premises environments, and in other cloud environments. You can quickly assess the status of available updates and manage the process of installing required updates for your machines reporting to Update Management.
1617

articles/automation/whats-new.md

Lines changed: 8 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -21,6 +21,14 @@ Azure Automation receives improvements on an ongoing basis. To stay up to date w
2121

2222
This page is updated monthly, so revisit it regularly. If you're looking for items older than six months, you can find them in [Archive for What's new in Azure Automation](whats-new-archive.md).
2323

24+
## December 2023
25+
26+
### Retirement of Azure Update Management and Change Tracking using Log Analytics
27+
28+
**Type: Retirement**
29+
30+
On **31 August 2024**, Azure Automation will retire [Automation Update management](https://learn.microsoft.com/answers/questions/1459053/retirement-announcement-azure-automation-update-ma) and [Change Tracking using Log Analytics](https://learn.microsoft.com/answers/questions/1459059/retirement-announcement-azure-automation-change-tr). You must migrate to [Azure Update Manager](../update-manager/overview.md) and [Change tracking and inventory using Azure Monitoring Agent](change-tracking/overview-monitoring-agent.md) respectively before the deprecation date.
31+
2432
## November 2023
2533

2634
### General Availability: Azure Automation supports PowerShell 7.2 runbooks

articles/azure-resource-manager/management/azure-subscription-service-limits.md

Lines changed: 7 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -85,6 +85,7 @@ The following limits apply when you use Azure Resource Manager and Azure resourc
8585

8686
[!INCLUDE [redis-cache-service-limits](../../azure-cache-for-redis/includes/redis-cache-service-limits.md)]
8787

88+
8889
## Azure Cloud Services limits
8990

9091
[!INCLUDE [azure-cloud-services-limits](../../../includes/azure-cloud-services-limits.md)]
@@ -93,7 +94,7 @@ The following limits apply when you use Azure Resource Manager and Azure resourc
9394

9495
Pricing tiers determine the capacity and limits of your search service. Tiers include:
9596

96-
* **Free** multi-tenant service, shared with other Azure subscribers, is intended for evaluation and small development projects.
97+
* **Free** multitenant service, shared with other Azure subscribers, is intended for evaluation and small development projects.
9798
* **Basic** provides dedicated computing resources for production workloads at a smaller scale, with up to three replicas for highly available query workloads.
9899
* **Standard**, which includes S1, S2, S3, and S3 High Density, is for larger production workloads. Multiple levels exist within the Standard tier so that you can choose a resource configuration that best matches your workload profile.
99100

@@ -113,6 +114,10 @@ To learn more about limits on a more granular level, such as document size, quer
113114

114115
[!INCLUDE [azure-cognitive-services-limits](../../../includes/azure-cognitive-services-limits.md)]
115116

117+
## Azure Chaos Studio limits
118+
119+
For Azure Chaos Studio limits, see [Azure Chaos Studio service limits](../../chaos-studio/chaos-studio-service-limits.md).
120+
116121
## Azure Communications Gateway limits
117122

118123
Some of the following default limits and quotas can be increased. To request a change, create a [change request](../../communications-gateway/request-changes.md) stating the limit you want to change.
@@ -367,7 +372,7 @@ For limits specific to Media Services v2 (legacy), see [Media Services v2 (legac
367372

368373
[!INCLUDE [mobile-services-limits](../../../includes/mobile-services-limits.md)]
369374

370-
## Multi-Factor Authentication limits
375+
## Multifactor authentication limits
371376

372377
[!INCLUDE [azure-mfa-service-limits](../../../includes/azure-mfa-service-limits.md)]
373378

articles/business-continuity-center/toc.yml

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -16,6 +16,8 @@
1616
href: tutorial-review-security-posture.md
1717
- name: Monitor jobs
1818
href: tutorial-monitor-operate.md
19+
- name: Monitor alerts and metrics
20+
href: tutorial-monitor-alerts-metrics.md
1921
- name: Monitoring protection summary
2022
href: tutorial-monitor-protection-summary.md
2123
- name: Govern and view compliance
Lines changed: 86 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,86 @@
1+
---
2+
title: Tutorial - Monitor alerts and metrics in Azure Business Continuity Center
3+
description: In this tutorial, learn how to monitor alerts and configure notifications for your business continuity estate using Azure Business Continuity center.
4+
ms.topic: tutorial
5+
ms.date: 12/11/2023
6+
ms.service: azure-business-continuity-center
7+
ms.custom:
8+
- ignite-2023
9+
author: AbhishekMallick-MS
10+
ms.author: v-abhmallick
11+
---
12+
13+
# Tutorials: Monitor alerts and metrics for your business continuity estate (preview)
14+
15+
16+
This tutorial describes how Azure Business Continuity Center (preview) allows you to view alerts across Azure Backup and Azure Site Recovery, configure notifications, view metrics, and take appropriate action.
17+
18+
## Monitor alerts
19+
20+
Azure Business Continuity Center allows you to monitor alerts that are raised for your critical events in your backup and disaster recovery events. You can view any built-in alerts that were fired by solutions, such as Azure Backup or Azure Site Recovery, and alerts fired based on custom alert rules on metrics.
21+
22+
Follow these steps:
23+
24+
1. In **Azure Business Continuity Center**, select **Alerts view**.
25+
26+
The count of all alert rules appears that have at least one or more fired alerts in the selected time range.
27+
28+
2. Filter the list by *severity of alert*, *category of alert*, *time range* (up to last 15 days), and other parameters.
29+
30+
3. The *Impacted Items count* in the grid shows the number of resources on which an alert corresponding to that alert rule was fired. To view the impacted items, select **View impacted items** in the context menu to view all alerts that were triggered due to that alert rule.
31+
32+
You can then review each alert and take appropriate action.
33+
34+
## Configure notifications
35+
36+
To route alerts to the notification channels, create an alert processing rule and an action group. An alert processing rule is a rule that specifies which alerts should be routed to a particular notification channel, and the action group represents the notification channel.
37+
38+
>[!Note]
39+
>Any action group supported by Azure Monitor (for example, email, webhooks, functions, logic apps, etc.) are supported for the backup and disaster recovery alerts also.
40+
41+
To configure email notifications for your alerts, follow these steps:
42+
43+
1. Go to **Azure Business Continuity Center** > **Alerts**, and then select **Create Alert Processing Rule**.
44+
45+
2. Under **Scope**, select *scope of the alert processing rule*, and then apply the rule for all the resources in a subscription.
46+
47+
You can make other customizations to the scope by applying filters. For example, generating notification for alert of a certain severity, generating notifications only for selected alert rules, etc.
48+
49+
3. On **Rule settings**, select **Apply action group** and **Create action group** (or use an existing one). It is the destination to which the notification for an alert should be sent. For example, an email address.
50+
51+
4. To create an action group, on the **Basics** tab, select the *name of the action group*, the *subscription*, and the *resource group* under which it must be created.
52+
53+
5. On the **Notifications** tab, select the *destination of the notification* as **Email**, **SMS Message**, or **Push/ Voice**, and then enter the *recipient's email ID* and other required details.
54+
55+
6. Select **Review+Create** > **Create** to deploy the action group. The creation of the action group leads you back to the alert processing rule creation. The created action group appears in the Rule settings page.
56+
57+
7. On the **Scheduling** tab, select **Always**.
58+
59+
8. On the **Details** tab, specify the subscription, resource group and name of the alert processing rule being created.
60+
61+
9. Add *Tags* if needed and select **Review + Create** > **Create**. The alert processing rule will be active in a few minutes.
62+
63+
## View metrics
64+
65+
You can use Azure Business Continuity Center to view built-in metrics for business continuity scenarios, and enable alerts based on these metric values.
66+
67+
>[!Note]
68+
>Currently, only metrics for Azure Backup are supported (Backup Health Events and Restore Health Events). [Learn more](../backup/metrics-overview.md) about the supported metrics and their definitions.
69+
70+
To view metrics, follow these steps:
71+
72+
1. Go to **Azure Business Continuity Center** and select the **Metrics** tab to open the **Azure Monitor metrics explorer**.
73+
74+
2. Select the *resource(s)* for which you want to see metrics. For example, in Azure Backup scenarios, you have to choose a *vault* (or a *group of vaults* in a subscription and region).
75+
76+
3. Select the *metric* you want to view, for example, *Backup Health events*.
77+
78+
4. Use the *filters* to further see the metric values at lower levels of granularity, for example, a particular protected item in the vault.
79+
80+
5. To create alert rules based on the value of the metric, select **New Alert Rule** at the top of the *metrics chart*, which leads you to the metric alert rules creation experience. [Learn more](../backup/metrics-overview.md#configure-alerts-and-notifications-on-your-metrics) about supported metric alert scenarios.
81+
82+
## Next steps
83+
84+
- [Configure datasources](./tutorial-configure-protection-datasource.md)
85+
86+

articles/chaos-studio/TOC.yml

Lines changed: 0 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -4,8 +4,6 @@
44
items:
55
- name: What is Azure Chaos Studio?
66
href: chaos-studio-overview.md
7-
- name: What is chaos engineering?
8-
href: /azure/architecture/framework/resiliency/chaos-engineering?toc=/azure/chaos-studio/toc.json&bc=/azure/chaos-studio/breadcrumb/toc.json
97
- name: Quickstart
108
items:
119
- name: Create and run a chaos experiment using Azure Chaos Studio

0 commit comments

Comments
 (0)