Skip to content

Commit b8adc12

Browse files
Merge branch 'main' of https://github.com/MicrosoftDocs/azure-docs-pr into pauljewell-ha-apps
2 parents 97ea2c7 + 2358926 commit b8adc12

28 files changed

+169
-280
lines changed

articles/active-directory/verifiable-credentials/decentralized-identifier-overview.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -19,7 +19,7 @@ ms.reviewer:
1919

2020
Our digital and physical lives are increasingly linked to the apps, services, and devices we use to access a rich set of experiences. This digital transformation allows us to interact with hundreds of companies and thousands of other users in ways that were previously unimaginable.
2121

22-
But identity data has too often been exposed in security breaches. These breaches affect our social, professional, and financial lives. Microsoft believes that there’s a better way. Every person has a right to an identity that they own and control, one that securely stores elements of their digital identity and preserves privacy. This primer explains how we are joining hands with a diverse community to build an open, trustworthy, interoperable, and standards-based Decentralized Identity (DID) solution for individuals and organizations.
22+
But identity data has too often been exposed in security breaches. These breaches affect our social, professional, and financial lives. Microsoft believes that there’s a better way. Every person has a right to an identity that they own and control, one that securely stores elements of their digital identity and preserves privacy. This primer explains how we are joining hands with a diverse community to build an open, trustworthy, interoperable, and standards-based Decentralized Identity solution for individuals and organizations.
2323

2424
## Why we need Decentralized Identity
2525

articles/api-management/api-management-howto-mutual-certificates-for-clients.md

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -45,7 +45,8 @@ For more information, see [API Management access restriction policies](api-manag
4545
You can also create policy expressions with the [`context` variable](api-management-policy-expressions.md#ContextVariables) to check client certificates. Examples in the following sections show expressions using the `context.Request.Certificate` property and other `context` properties.
4646

4747
> [!IMPORTANT]
48-
> Starting May 2021, the `context.Request.Certificate` property only requests the certificate when the API Management instance's [`hostnameConfiguration`](/rest/api/apimanagement/current-ga/api-management-service/create-or-update#hostnameconfiguration) sets the `negotiateClientCertificate` property to True. By default, `negotiateClientCertificate` is set to False.
48+
> * Starting May 2021, the `context.Request.Certificate` property only requests the certificate when the API Management instance's [`hostnameConfiguration`](/rest/api/apimanagement/current-ga/api-management-service/create-or-update#hostnameconfiguration) sets the `negotiateClientCertificate` property to True. By default, `negotiateClientCertificate` is set to False.
49+
> * If TLS renegotiation is disabled in your client, you may see TLS errors when requesting the certificate using the `context.Request.Certificate` property. If this occurs, enable TLS renegotation settings in the client.
4950
5051
### Checking the issuer and subject
5152

articles/azure-monitor/alerts/alerts-create-new-alert-rule.md

Lines changed: 4 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -200,12 +200,14 @@ And then defining these elements for the resulting alert actions using:
200200
1. In the **Details** tab, define the **Project details**.
201201
- Select the **Subscription**.
202202
- Select the **Resource group**.
203-
- (Optional) If you want to make sure that the data processing for the alert rule takes place within a specific region, and you're creating a metric alert rule that monitors a custom metric, you can select to process the alert rule in one of these regions.
203+
- (Optional) If you're creating a metric alert rule that monitors a custom metric with the scope defined as one of the regions below, and you want to make sure that the data processing for the alert rule takes place within that region, you can select to process the alert rule in one of these regions:
204204
- North Europe
205205
- West Europe
206206
- Sweden Central
207207
- Germany West Central
208-
208+
209+
> [!NOTE]
210+
> We are continually adding more regions for regional data processing.
209211
1. Define the **Alert rule details**.
210212

211213
### [Metric alert](#tab/metric)

articles/azure-monitor/alerts/alerts-troubleshoot-metric.md

Lines changed: 19 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,15 +1,15 @@
11
---
2-
title: Troubleshooting Azure metric alerts
2+
title: Frequently asked questions about Azure metric alerts
33
description: Common issues with Azure Monitor metric alerts and possible solutions.
44
author: harelbr
55
ms.author: harelbr
66
ms.topic: troubleshooting
77
ms.date: 8/31/2022
88
ms:reviwer: harelbr
99
---
10-
# Troubleshooting problems in Azure Monitor metric alerts
10+
# Frequently asked questions about Azure Monitor metric alerts
1111

12-
This article discusses common problems in Azure Monitor [metric alerts](alerts-metric-overview.md) and how to troubleshoot them.
12+
This article discusses common questions about Azure Monitor [metric alerts](alerts-metric-overview.md) and how to troubleshoot them.
1313

1414
Azure Monitor alerts proactively notify you when important conditions are found in your monitoring data. They allow you to identify and address issues before the users of your system notice them. For more information on alerting, see [Overview of alerts in Microsoft Azure](./alerts-overview.md).
1515

@@ -140,6 +140,22 @@ To avoid having the deployment fail when trying to validate the custom metric’
140140
> [!NOTE]
141141
> Using the *skipMetricValidation* parameter might also be required when defining an alert rule on an existing custom metric that hasn't been emitted in several days.
142142
143+
## Process data for a metric alert rule in a specific region
144+
145+
You can make sure that an alert rule is processed in a specified region if your metric alert rule is defined with a scope of that region and if it monitors a custom metric.
146+
147+
These are the currently support regions for regional processing of metric alert rules:
148+
- North Europe
149+
- West Europe
150+
- Sweden Central
151+
- Germany West Central
152+
153+
To enable regional data processing in one of these regions, select the specified region in the **Details** section of the [create a new alert rule wizard](./alerts-create-new-alert-rule.md).
154+
155+
> [!NOTE]
156+
> We are continually adding more regions for regional data processing.
157+
158+
143159
## Export the Azure Resource Manager template of a metric alert rule via the Azure portal
144160

145161
Exporting the Resource Manager template of a metric alert rule helps you understand its JSON syntax and properties, and can be used to automate future deployments.

articles/azure-monitor/toc.yml

Lines changed: 19 additions & 22 deletions
Original file line numberDiff line numberDiff line change
@@ -469,14 +469,14 @@ items:
469469
items:
470470
- name: Overview
471471
href: agents/agents-overview.md
472-
- name: Install Azure Monitor Agent
472+
- name: Install
473473
displayName: Azure Monitor agent
474474
items:
475-
- name: Using the agent extension
475+
- name: Using the VM extension
476476
href: agents/azure-monitor-agent-manage.md
477477
- name: Using Windows client installer (preview)
478478
href: agents/azure-monitor-agent-windows-client.md
479-
- name: Configure data collection
479+
- name: Configure
480480
items:
481481
- name: Collect events and performance
482482
displayName: data collection rule,Azure Monitor agent
@@ -585,26 +585,23 @@ items:
585585
href: essentials/collect-custom-metrics-linux-telegraf.md
586586
- name: Troubleshoot
587587
items:
588-
- name: Azure Monitor Agent
588+
- name: Linux VM
589+
href: agents/azure-monitor-agent-troubleshoot-linux-vm.md
590+
- name: Linux Rsyslog issues
591+
href: agents/azure-monitor-agent-troubleshoot-linux-vm-rsyslog.md
592+
- name: Windows VM
593+
href: agents/azure-monitor-agent-troubleshoot-windows-vm.md
594+
- name: Windows Arc-enabled server
595+
href: agents/azure-monitor-agent-troubleshoot-windows-arc.md
596+
- name: Troubleshoot legacy agents
589597
displayName: Troubleshooting guidance
590598
items:
591-
- name: Linux VM
592-
href: agents/azure-monitor-agent-troubleshoot-linux-vm.md
593-
- name: Linux Rsyslog issues
594-
href: agents/azure-monitor-agent-troubleshoot-linux-vm-rsyslog.md
595-
- name: Windows VM
596-
href: agents/azure-monitor-agent-troubleshoot-windows-vm.md
597-
- name: Windows Arc-enabled server
598-
href: agents/azure-monitor-agent-troubleshoot-windows-arc.md
599-
- name: Log Analytics VM Extension
600-
displayName: troubleshoot, troubleshooting
601-
href: visualize/vmext-troubleshoot.md
602-
- name: Log Analytics Windows agent
603-
displayName: troubleshoot, troubleshooting
604-
href: agents/agent-windows-troubleshoot.md
605-
- name: Log Analytics Linux agent
606-
displayName: troubleshoot, troubleshooting
607-
href: agents/agent-linux-troubleshoot.md
599+
- name: Log Analytics VM Extension
600+
href: visualize/vmext-troubleshoot.md
601+
- name: Log Analytics Windows agent
602+
href: agents/agent-windows-troubleshoot.md
603+
- name: Log Analytics Linux agent
604+
href: agents/agent-linux-troubleshoot.md
608605
- name: Autoscale
609606
items:
610607
- name: Overview
@@ -651,7 +648,7 @@ items:
651648
href: alerts/alerts-metric-logs.md
652649
- name: Using Resource Manager template
653650
href: alerts/alerts-metric-create-templates.md
654-
- name: Troubleshoot metric alerts
651+
- name: FAQ
655652
href: alerts/alerts-troubleshoot-metric.md
656653
- name: Log alert rules
657654
items:

articles/azure-vmware/install-vmware-hcx.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -10,7 +10,7 @@ ms.date: 03/29/2022
1010

1111
VMware HCX Advanced and its associated Cloud Manager are no longer pre-deployed in Azure VMware Solution. Instead, you'll install it through the Azure portal as an add-on. You'll still download the HCX Connector OVA and deploy the virtual appliance on your on-premises vCenter Server.
1212

13-
Any edition of VMware HCX supports 25 site pairings (on-premises to cloud or cloud to cloud) in a single HCX manager system. The default is HCX Advanced, but you can open a [support request](https://rc.portal.azure.com/#create/Microsoft.Support) to have HCX Enterprise Edition enabled. Once the service is generally available, you'll have 30 days to decide on your next steps. You can turn off or opt out of the HCX Enterprise Edition service but keep HCX Advanced as it's part of the node cost.
13+
Any edition of VMware HCX supports 25 site pairings (on-premises to cloud or cloud to cloud) in a single HCX manager system. The default is HCX Advanced, but you can open a [support request](https://rc.portal.azure.com/#create/Microsoft.Support) to have HCX Enterprise Edition enabled. VMware HCX Enterprise edition is available and supported on Azure VMware Solution, at no additional cost.
1414

1515
Downgrading from HCX Enterprise Edition to HCX Advanced is possible without redeploying. First, ensure you've reverted to an HCX Advanced configuration state and not using the Enterprise features. If you plan to downgrade, ensure that no scheduled migrations, features like RAV and [HCX Mobility Optimized Networking (MON)](https://docs.vmware.com/en/VMware-HCX/4.1/hcx-user-guide/GUID-0E254D74-60A9-479C-825D-F373C41F40BC.html) are in use.
1616

@@ -30,7 +30,7 @@ After you're finished, follow the recommended next steps at the end to continue
3030

3131
- [Prepare for HCX installations](https://docs.vmware.com/en/VMware-HCX/4.1/hcx-user-guide/GUID-A631101E-8564-4173-8442-1D294B731CEB.html)
3232

33-
- If you plan to use VMware HCX Enterprise, make sure you've enabled the [VMware HCX Enterprise](https://cloud.vmware.com/community/2019/08/08/introducing-hcx-enterprise/) add-on through a [support request](https://portal.azure.com/#create/Microsoft.Support). It's a free 12-month trial in Azure VMware Solution.
33+
- If you plan to use VMware HCX Enterprise, make sure you've enabled the [VMware HCX Enterprise](https://cloud.vmware.com/community/2019/08/08/introducing-hcx-enterprise/) add-on through a [support request](https://portal.azure.com/#create/Microsoft.Support).
3434

3535
- [VMware blog series - cloud migration](https://blogs.vmware.com/vsphere/2019/10/cloud-migration-series-part-2.html)
3636

articles/cognitive-services/Speech-Service/pronunciation-assessment-tool.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,7 @@ manager: nitinme
88
ms.service: cognitive-services
99
ms.subservice: speech-service
1010
ms.topic: how-to
11-
ms.date: 06/08/2022
11+
ms.date: 09/08/2022
1212
ms.author: v-baolianzou
1313
---
1414

@@ -29,7 +29,7 @@ This article describes how to use the pronunciation assessment tool through the
2929
You can explore and try out pronunciation assessment even without signing in.
3030

3131
> [!TIP]
32-
> To assess more than 5 seconds of speech with your own script, sign in with an Azure account and use your Speech or Cognitive Services resource.
32+
> To assess more than 5 seconds of speech with your own script, sign in with an [Azure account](https://azure.microsoft.com/free/cognitive-services) and use your <a href="https://portal.azure.com/#create/Microsoft.CognitiveServicesSpeechServices" title="Create a Speech resource" target="_blank">Speech resource</a>.
3333
3434
Follow these steps to assess your pronunciation of the reference text:
3535

0 commit comments

Comments
 (0)