Merge pull request #286370 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/automation/automation-disaster-recovery.md

@@ -93,7 +93,7 @@ You can use these scripts for migration of Automation account assets from the ac
 1. Ensure that both the source and destination Automation accounts should belong to the same Microsoft Entra tenant.
 
 ### Create and execute the runbook
-You can use the[PowerShell script](https://github.com/azureautomation/Migrate-automation-account-assets-from-one-region-to-another) or [PowerShell workflow](https://github.com/azureautomation/Migrate-automation-account-assets-from-one-region-to-another-PwshWorkflow/tree/main) runbook or import from the Runbook gallery and execute it to enable migration of assets from one Automation account to another. 
+You can use the [PowerShell script](https://github.com/azureautomation/Migrate-automation-account-assets-from-one-region-to-another) or [PowerShell workflow](https://github.com/azureautomation/Migrate-automation-account-assets-from-one-region-to-another-PwshWorkflow/tree/main) runbook or import from the Runbook gallery and execute it to enable migration of assets from one Automation account to another. 
 
 Follow the steps to import and execute the runbook:
 

articles/automation/automation-scenario-aws-deployment.md

@@ -95,7 +95,7 @@ Ensure that the AWS PowerShell module has been imported into Azure Automation.
 
 ## Next steps
  
-* To find out what runbooks are supported, see[Azure Automation runbook types](automation-runbook-types.md).
+* To find out what runbooks are supported, see [Azure Automation runbook types](automation-runbook-types.md).
 * To work with runbooks, see [Manage runbooks in Azure Automation](manage-runbooks.md).
 * For details of PowerShell, see [PowerShell Docs](/powershell/scripting/overview).
 * For script support, see [Native PowerShell script support in Azure Automation](https://azure.microsoft.com/blog/announcing-powershell-script-support-azure-automation-2/).

articles/container-registry/container-registry-manage-artifact.md

@@ -58,7 +58,7 @@ az login
 az acr login -n $REGISTRY  
 ``` 
 
-If Docker isn't available, you can utilize the AD token provided for authentication. Authenticate with your[individual Microsoft Entra identity](container-registry-authentication.md?tabs=azure-cli#individual-login-with-azure-ad) using an AD token. Always use "000..." for the `USER_NAME` as the token is parsed through the `PASSWORD` variable.
+If Docker isn't available, you can utilize the AD token provided for authentication. Authenticate with your [individual Microsoft Entra identity](container-registry-authentication.md?tabs=azure-cli#individual-login-with-azure-ad) using an AD token. Always use "000..." for the `USER_NAME` as the token is parsed through the `PASSWORD` variable.
 
 ```azurecli
 # Login to Azure
@@ -528,5 +528,3 @@ In this article, you learned how to use Azure Container Registry to store, manag
 [iana-mediatypes]:          https://www.rfc-editor.org/rfc/rfc6838
 [acr-landing]:              https://aka.ms/acr
 [Notation]:                  /azure/container-registry/container-registry-tutorial-sign-build-push
-
-

articles/dns/dns-faq-private.yml

@@ -101,7 +101,7 @@ sections:
       - question: |
           How do I migrate my existing private DNS zones to the new model?
         answer: |
-          We strongly recommend that you migrate to the new resource model as soon as possible. Legacy resource model will be supported, however, further features won't be developed on top of this model. In future, we intend to deprecate it in favor of new resource model. For guidance on how to migrate your existing private DNS zones to new resource model see[migration guide for Azure DNS private zones](private-dns-migration-guide.md).
+          We strongly recommend that you migrate to the new resource model as soon as possible. Legacy resource model will be supported, however, further features won't be developed on top of this model. In future, we intend to deprecate it in favor of new resource model. For guidance on how to migrate your existing private DNS zones to new resource model see [migration guide for Azure DNS private zones](private-dns-migration-guide.md).
 
       - question: |
           Which one takes precedence, Azure private DNS or a custom DNS server setup on a VM?

articles/dns/dns-operations-recordsets-portal.md

@@ -25,7 +25,7 @@ To create a record set in the Azure portal, see [Create an Azure DNS zone and re
 
 2. Select your DNS zone and then select **Recordsets**. The current record sets are displayed.
 
-   ![A screenshot of DNS zone record sets.](./media/dns-operations-recordsets-portal/recordsets.png)
+   [ ![A screenshot of DNS zone record sets.](./media/dns-operations-recordsets-portal/recordsets.png) ](./media/dns-operations-recordsets-portal/recordsets.png)
 
 ## Add a new record to a record set
 
@@ -37,7 +37,7 @@ You can add up to 20 records to any record set. A record set may not contain two
 
 2. Specify the record set properties by filling in the fields.
 
-   ![A screenshot of adding records to a recordset.](./media/dns-operations-recordsets-portal/record-page.png)
+   [ ![A screenshot of adding records to a recordset.](./media/dns-operations-recordsets-portal/record-page.png) ](./media/dns-operations-recordsets-portal/record-page.png)
 
 3. Select **Apply** at the bottom of the page to save your settings.
 
@@ -68,7 +68,7 @@ You can use the Azure portal to remove records from a record set. Removing the l
 2. A message appears asking if you want to delete the record set.
 3. Verify that the name matches the record set that you want to delete, and then select **Yes**.
 
-   ![A screenshot of deleting a recordset.](./media/dns-operations-recordsets-portal/delete-record-set.png)
+   [ ![A screenshot of deleting a recordset.](./media/dns-operations-recordsets-portal/delete-record-set.png) ](./media/dns-operations-recordsets-portal/delete-record-set.png)
 
 4. On the **DNS zone** page, verify that the record set is no longer visible.
 
@@ -100,4 +100,4 @@ You can't delete the SOA and NS record sets at the zone apex (name = "\@") that
 * For more information about Azure DNS, see the [Azure DNS overview](dns-overview.md).
 * For more information about automating DNS, see [Creating DNS zones and record sets using the .NET SDK](dns-sdk.md).
 * For more information about reverse DNS records, see [Overview of reverse DNS and support in Azure](dns-reverse-dns-overview.md).
-* For more information about Azure DNS alias records, see [Azure DNS alias records overview](dns-alias.md).
+* For more information about Azure DNS alias records, see [Azure DNS alias records overview](dns-alias.md).

articles/dns/private-resolver-hybrid-dns.md

@@ -90,19 +90,19 @@ Next, create a rule in your ruleset for your on-premises domain. In this example
 
 The procedure to configure on-premises DNS depends on the type of DNS server you're using. In the following example, a Windows DNS server at **10.100.0.2** is configured with a conditional forwarder for the private DNS zone **azure.contoso.com**. The conditional forwarder is set to forward queries to **10.10.0.4**, which is the inbound endpoint IP address for your Azure DNS Private Resolver. There's another IP address also configured here to enable DNS failover. For more information about enabling failover, see [Tutorial: Set up DNS failover using private resolvers](tutorial-dns-private-resolver-failover.md). For the purposes of this demonstration, only the **10.10.0.4** inbound endpoint is required.
 
-![View on-premises forwarding](./media/private-resolver-hybrid-dns/on-premises-forwarders.png) 
+![View on-premises forwarding](./media/private-resolver-hybrid-dns/on-premises-forwarders.png#lightbox)
 
 ## Demonstrate hybrid DNS
 
 Using a VM located in the virtual network where the Azure DNS Private Resolver is provisioned, issue a DNS query for a resource record in your on-premises domain. In this example, a query is performed for the record **testdns.contoso.com**:
 
-![Verify Azure to on-premise](./media/private-resolver-hybrid-dns/azure-to-on-premises-lookup.png) 
+![Verify Azure to on-premise](./media/private-resolver-hybrid-dns/azure-to-on-premises-lookup.png#lightbox)
 
 The path for the query is: Azure DNS > inbound endpoint > outbound endpoint > ruleset rule for contoso.com > on-premises DNS (10.100.0.2). The DNS server at 10.100.0.2 is an on-premises DNS resolver, but it could also be an authoritative DNS server.
 
 Using an on-premises VM or device, issue a DNS query for a resource record in your Azure private DNS zone. In this example, a query is performed for the record **test.azure.contoso.com**:
 
-![Verify on-premises to Azure](./media/private-resolver-hybrid-dns/on-premises-to-azure-lookup.png) 
+![Verify on-premises to Azure](./media/private-resolver-hybrid-dns/on-premises-to-azure-lookup.png#lightbox) 
 
 The path for this query is: client's default DNS resolver (10.100.0.2) > on-premises conditional forwarder rule for azure.contoso.com > inbound endpoint (10.10.0.4) 
 

articles/event-grid/authenticate-with-entra-id-namespaces.md

@@ -61,7 +61,7 @@ The identity used to publish events to Event Grid must have the permission ``Mic
 With RBAC privileges taken care of, you can now [build your client application to send events](#publish-events-using-event-grids-client-sdks) to Event Grid.
 
 > [!NOTE]
-> Event Grid supports more RBAC roles for purposes beyond sending events. For more information, see[Event Grid built-in roles](security-authorization.md#built-in-roles).
+> Event Grid supports more RBAC roles for purposes beyond sending events. For more information, see [Event Grid built-in roles](security-authorization.md#built-in-roles).
 
 
 ## Publish events using Event Grid's client SDKs

articles/event-grid/authenticate-with-microsoft-entra-id.md

@@ -64,7 +64,7 @@ The identity used to publish events to Event Grid must have the permission ``Mic
 With RBAC privileges taken care of, you can now [build your client application to send events](#publish-events-using-event-grids-client-sdks) to Event Grid.
 
 > [!NOTE]
-> Event Grid supports more RBAC roles for purposes beyond sending events. For more information, see[Event Grid built-in roles](security-authorization.md#built-in-roles).
+> Event Grid supports more RBAC roles for purposes beyond sending events. For more information, see [Event Grid built-in roles](security-authorization.md#built-in-roles).
 
 
 ## Publish events using Event Grid's client SDKs

articles/expressroute/rate-limit.md

@@ -51,21 +51,21 @@ To enable rate limiting for an existing ExpressRoute Direct circuit, complete th
 
 1. Select **Yes** for *Enable Rate Limiting*. The following diagram illustrates the configuration page for enabling rate limiting for an ExpressRoute Direct circuit.
 
-    :::image type="content" source="./media/rate-limit/existing-circuit.png" alt-text="Screenshot of the configuration page for an ExpressRoute Direct circuit showing the rate limiting setting.":::
+    :::image type="content" source="./media/rate-limit/existing-circuit.png" alt-text="Screenshot of the configuration page for an ExpressRoute Direct circuit showing the Enable Rate Limiting setting set to Yes.":::
 
 1. Finally, select the **Save** button at the top of the page to apply the changes.
 
 ## Disable rate limiting
 
-To disable rate limiting for an existing ExpressRoute Direct circuit, complete the following these:
+To disable rate limiting for an existing ExpressRoute Direct circuit, complete the following steps:
 
 1. Sign-in to the Azure portal using this [Azure portal](https://portal.azure.com/?feature.erdirectportratelimit=true) link, then go to the ExpressRoute Direct circuit that you want to configure rate limiting for.
 
 1. Select **Configuration** under *Settings* on the left side pane.
 
 1. Select **No** for *Enable Rate Limiting*. The following diagram illustrates the configuration page for disabling rate limiting for an ExpressRoute Direct circuit.
 
-    :::image type="content" source="./media/rate-limit/disable-rate-limiting.png" alt-text="Screenshot of the configuration page for an ExpressRoute Direct circuit showing how to disable rate limiting.":::
+    :::image type="content" source="./media/rate-limit/disable-rate-limiting.png" alt-text="Screenshot of the configuration page for an ExpressRoute Direct circuit showing the Enable Rate Limiting setting set to No.":::
 
 1. Finally,  select the **Save** button at the top of the page to apply the changes.
 
@@ -81,11 +81,11 @@ To disable rate limiting for an existing ExpressRoute Direct circuit, complete t
 
 * How does rate limiting affect my circuit performance?
 
-    An ExpressRoute circuit has two connection links between Microsoft edge routers and customer edge (CE) routers. For example, if your circuit bandwidth is set to 1 Gbps and you distribute your traffic evenly across both links, you can reach up to 2*1 (that is, 2) Gbps. However, it isn't a recommended practice and we suggest using the extra bandwidth for high availability only. If you exceed the configured bandwidth over private or Microsoft peering on either of the links by more than 20%, then rate limiting lowers the throughput to the configured bandwidth.
+    An ExpressRoute circuit has two connection links between Microsoft edge routers and customer edge (CE) routers. For example, if your circuit bandwidth is set to 1 Gbps and you distribute your traffic evenly across both links, you can reach up to 2*1 (that is, 2) Gbps. However, this is not a recommended practice and we suggest using the extra bandwidth for high availability only. If you exceed the configured bandwidth over private or Microsoft peering on either of the links by more than 20%, then rate limiting lowers the throughput to the configured bandwidth.
 
 * How can I check the rate limiting status of my ExpressRoute Direct port circuits?
 
-    In Azure portal, on the ‘Circuits’ pane of your ExpressRoute Direct port, you would see all the circuits configured over the ExpressRoute Direct port along with the rate limiting status. See the following screenshot:
+    In the Azure portal, on the ‘Circuits’ pane of your ExpressRoute Direct port, you will see all the circuits configured over the ExpressRoute Direct port along with the rate limiting status. See the following screenshot as an example:
 
     :::image type="content" source="./media/rate-limit/status.png" alt-text="Screenshot of the rate limiting status from an ExpressRoute Direct resource.":::
 
@@ -116,7 +116,7 @@ To disable rate limiting for an existing ExpressRoute Direct circuit, complete t
 
 * How does increasing the circuit bandwidth affect the traffic flow through the circuit? 
 
-    Increasing the circuit bandwidth doesn’t affect the traffic flow through the circuit. The bandwidth increase is seamless and the circuit bandwidth upgrade reflects in a few minutes. However, the bandwidth increase is irreversible.
+    Increasing the circuit bandwidth does not affect the traffic flow through the circuit. The bandwidth increase is seamless and the circuit bandwidth upgrade will be reflected in a few minutes. It is important to note the bandwidth increase is irreversible.
 
 * Can I enable or disable rate limiting for a specific circuit configured over my ExpressRoute Direct port? 
 

articles/frontdoor/classic-retirement-faq.md

@@ -32,7 +32,7 @@ Azure Front Door (classic) is a legacy service that provides dynamic site accele
 Azure Front Door Standard and Premium tiers represent the enhanced versions of Azure Front Door (classic). They maintain the same Service Level Agreement (SLA) and offer more benefits, including:
 
 * A unified static and dynamic delivery platform, with simplified cost model. 
-* Enhanced security features, such as[Private Link integration](private-link.md), advanced WAF enhancements with DRS 2.1, anomaly scoring based detection and bot management, and many more to come. 
+* Enhanced security features, such as [Private Link integration](private-link.md), advanced WAF enhancements with DRS 2.1, anomaly scoring based detection and bot management, and many more to come. 
 * Deep integration with Azure services to deliver secure, accelerated, and user friendly end-to-end cloud solutions. These integrations include:
     * DNS deterministic name library integrations to prevent subdomain take over
     * [Prevalidated domain integration with PaaS service with  one-time domain validation](./standard-premium/how-to-add-custom-domain.md#associate-the-custom-domain-with-your-azure-front-door-endpoint).