Merge pull request #277106 from MicrosoftDocs/repo_sync_working_branch

Confirm merge from repo_sync_working_branch to main to sync with https://github.com/MicrosoftDocs/azure-docs (branch main)

Author: Taojunshen

articles/azure-monitor/vm/vminsights-troubleshoot.md

@@ -60,9 +60,11 @@ See the following articles for troubleshooting issues with the Log Analytics age
 ### Identifying the Issue
 
 To identify if this is the case you would first browse to the Monitor Dashboard, locate the Data Collection Rule in Question and view the JSON properties using the link on the top right-hand side of the overview blade:
+
 ![Screenshot of DCR Dashboard.](media/vminsights-troubleshoot/dcr-overview.png)
 
 You will see that stream name has been changed from its original name to reflect the performance counter stream name:
+
 ![Screenshot of DCR JSON.](media/vminsights-troubleshoot/dcr-json.png)
 
 We can see while the counter sections are pointing the perf table, the stream dataflow is still configured for the proper destination Microsof-InsightsMetrics.
@@ -92,32 +94,41 @@ This issue can't be resolved using the Monitor Dashboard directly, but we can fi
 #### Modify the Template
 
 1. Open the template file in the editor of your choice and locate the invalid stream name under the performance counter data source.
+   
 ![Screenshot of Template.json.](media/vminsights-troubleshoot/update-template.png)
 
 2. Using the valid stream name from the dataflow node fix the invalid reference, then save and close your file:
+   
 ![Screenshot of Updated Stream.](media/vminsights-troubleshoot/correct-template.png)
 
 #### Import the Template using the Custom Deployment Feature
 
 1. Back in the portal, search for and navigate to the custom template deployment:
+
 ![Screenshot of Deploy a custom template.](media/vminsights-troubleshoot/deploy-template.png)
 
 2. Choose the Option to "Build Your Own Template"
+
 ![Screenshot of Build your own template in the editor.](media/vminsights-troubleshoot/build-template.png)
 
 3. Using the "Load File" link browse to your saved template and parameter file:
+
 ![Screenshot of Load File.](media/vminsights-troubleshoot/load-file.png)
 
 4. Visually inspect the template to validate the change is in place and select the Save button
+
 ![Screenshot of Edit Template.](media/vminsights-troubleshoot/save-template.png)
 
 5. From here the portal will use the parameter file to fill in the deployment options (which can be changed) or left intact to overwrite the existing DCR, Once completed select the review and Create button.
+
 ![Screenshot of Custom Deployment.](media/vminsights-troubleshoot/deploy.png)
 
 6. After validation then we can select the Create button to finalize the deployment.
+
 ![Screenshot of Create Deployment.](media/vminsights-troubleshoot/create-deployment.png)
 
 7. After the deployment is complete, we can browse to the DCR again and review the JSON in overview blade:
+
 ![Screenshot of Review JSON.](media/vminsights-troubleshoot/updated-json.png)
 
 8. The agent will detect this change and download the new configuration, and this should restore ingestion to the insight metrics table.

articles/reliability/availability-zones-overview.md

@@ -24,6 +24,9 @@ The following diagram shows several example Azure regions. Regions 1 and 2 suppo
 
 To see which regions support availability zones, see [Azure regions with availability zone support](availability-zones-service-support.md#azure-regions-with-availability-zone-support).
 
+> [!NOTE]  
+> You need to deploy two or more Virtual Machines to different availability zones in the same region to get the highest possible [SLA connectivity percentage](https://www.microsoft.com/licensing/docs/view/Service-Level-Agreements-SLA-for-Online-Services?lang=1).
+
 ## Zonal and zone-redundant services
 
 When you deploy into an Azure region that contains availability zones, you can use multiple availability zones together. By using multiple availability zones, you can keep separate copies of your application and data within separate physical datacenters in a large metropolitan area.

articles/virtual-machines/nd-h100-v5-series.md

@@ -44,7 +44,7 @@ NVIDIA NVLink Interconnect: Supported <br>
 
 | Size                | vCPU | Memory: GiB | Temp storage (SSD) GiB | GPU                        | GPU Memory GiB | Max data disks | Max uncached disk throughput: IOPS/MBps | Max network bandwidth  | Max NICs |
 |---------------------|------|------------|------------------------|----------------------------|----------------|----------------|-----------------------------------------|------------------------------|----------|
-| Standard_ND96isr_H100_v5 | 96   | 1900       | 1000                   | 8 H100 80 GB GPUs(NVLink)  | 80             | 32             | 40800/612                               | 80,000 Mbps                         | 8        |
+| Standard_ND96isr_H100_v5 | 96   | 1900       | 28000                   | 8 H100 80 GB GPUs(NVLink)  | 80             | 32             | 40800/612                               | 80,000 Mbps                         | 8        |
 
 [!INCLUDE [virtual-machines-common-sizes-table-defs](../../includes/virtual-machines-common-sizes-table-defs.md)]
 

includes/dns-limits.md

@@ -11,7 +11,7 @@ ms.author: greglin
 | --- | --- |
 | Public DNS zones per subscription |250 <sup>1</sup> |
 | Record sets per public DNS zone |10,000 <sup>1</sup> |
-| Records per record set in public DNS zone |20 |
+| Records per record set in public DNS zone |20 <sup>1</sup> |
 | Number of Alias records for a single Azure resource |20|
 
 <sup>1</sup>If you need to increase these limits, contact Azure Support.
@@ -51,4 +51,4 @@ ms.author: greglin
 | Target DNS servers per forwarding rule |6|
 | QPS per endpoint |10,000|
 
-<sup>1</sup>Different limits might be enforced by the Azure portal until the portal is updated. Use PowerShell to provision elements up to the most current limits.
+<sup>1</sup>Different limits might be enforced by the Azure portal until the portal is updated. Use PowerShell to provision elements up to the most current limits.