Merge pull request #285591 from MicrosoftDocs/repo_sync_working_branch

Taojunshen · web-flow · commit 7117a8a56009 · 2024-08-28T00:33:07.000+08:00
Confirm merge from repo_sync_working_branch to main to sync with https://github.com/MicrosoftDocs/azure-docs (branch main)
diff --git a/articles/azure-app-configuration/concept-feature-management.md b/articles/azure-app-configuration/concept-feature-management.md
@@ -13,7 +13,7 @@ ms.date: 02/20/2024
 
 Traditionally, shipping a new application feature requires a complete redeployment of the application itself. Testing a feature often requires multiple deployments of the application. Each deployment might change the feature or expose the feature to different customers for testing.  
 
-Feature management is a modern software-development practice that decouples feature release from code deployment and enables quick changes to feature availability on demand. It uses a technique called *feature flags* (also known as *feature toggles* and *feature switches*) to dynamically administer a feature's lifecycle.
+Feature management is a software-development practice that decouples feature release from code deployment and enables quick changes to feature availability on demand. It uses a technique called *feature flags* (also known as *feature toggles* and *feature switches*) to dynamically administer a feature's lifecycle.
 
 Feature management helps developers address the following problems:
 
diff --git a/articles/azure-monitor/logs/manage-table-access.md b/articles/azure-monitor/logs/manage-table-access.md
@@ -90,7 +90,7 @@ The user can now read workspace details and run a query, but can't read data fro
 1. From the **Log Analytics workspaces** menu, select **Tables**.  
 1. Select the ellipsis ( **...** ) to the right of your table and select **Access control (IAM)**.
     
-   :::image type="content" source="media/manage-access/table-level-access-control.png" alt-text="Screenshot that shows the Log Analytics workspace table management screen with the table-level access control button highlighted." lightbox="media/manage-access/manage-access-create-custom-role-json.png":::      
+   :::image type="content" source="media/manage-access/table-level-access-control.png" alt-text="Screenshot that shows the Log Analytics workspace table management screen with the table-level access control button highlighted." lightbox="media/manage-access/table-level-access-control.png":::      
 
 1. On the **Access control (IAM)** screen, select **Add** > **Add role assignment**. 
 1. Select the **Reader** role and select **Next**.    
diff --git a/articles/ddos-protection/ddos-protection-features.md b/articles/ddos-protection/ddos-protection-features.md
@@ -21,7 +21,7 @@ Azure DDoS Protection monitors actual traffic utilization and constantly compare
 During mitigation, traffic sent to the protected resource is redirected by the DDoS protection service and several checks are performed, such as:
 
 - Ensure packets conform to internet specifications and aren't malformed.
-- Interact with the client to determine if the traffic is potentially a spoofed packet (e.g: SYN Auth or SYN Cookie or by dropping a packet for the source to retransmit it).
+- Interact with the client to determine if the traffic is potentially a spoofed packet (for example: SYN Auth or SYN Cookie or by dropping a packet for the source to retransmit it).
 - Rate-limit packets, if no other enforcement method can be performed.
 
 Azure DDoS Protection drops attack traffic and forwards the remaining traffic to its intended destination. Within a few minutes of attack detection, you're notified using Azure Monitor metrics. By configuring logging on DDoS Protection telemetry, you can write the logs to available options for future analysis. Metric data in Azure Monitor for DDoS Protection is retained for 30 days.
diff --git a/articles/expressroute/maintenance-alerts.md b/articles/expressroute/maintenance-alerts.md
@@ -41,7 +41,7 @@ ExpressRoute uses Azure Service Health to notify you of planned and upcoming Exp
 
     :::image type="content" source="./media/maintenance-alerts/health-history.png" alt-text="Screenshot of selecting Health history in Service Health." lightbox="./media/maintenance-alerts/health-history-expanded.png"::: 
 
-1. On this page, you can review individual maintenance events by filtering on a target subscription and Azure Region. To further narrow the scope of health history events, you can select the health event type and define a past time range. To filer for planned ExpressRoute circuit maintenance, set the Health Event Type to **Planned Maintenance**.
+1. On this page, you can review individual maintenance events by filtering on a target subscription and Azure Region. To further narrow the scope of health history events, you can select the health event type and define a past time range. To filter for planned ExpressRoute circuit maintenance, set the Health Event Type to **Planned Maintenance**.
 
     :::image type="content" source="./media/maintenance-alerts/past-maintenance.png" alt-text="Screenshot of past maintenance on Health history page." lightbox="./media/maintenance-alerts/past-maintenance-expanded.png"::: 
 
diff --git a/articles/openshift/responsibility-matrix.md b/articles/openshift/responsibility-matrix.md
@@ -314,9 +314,9 @@ Microsoft and Red Hat are responsible for enabling changes to the cluster infras
 
 <li>Set up public cloud load balancers
 
-<li>Set up native OpenShift router service. Provide the ability to set the router as private and add up to one additional router shard.
+<li>Set up the OpenShift Ingress cluster operator and the default IngressController. Provide the ability to add additional customer-managed IngressControllers and set the default IngressController as private.
 
-<li>Install, configure, and maintain OpenShift SDN components for default internal pod traffic.
+<li>Install, configure, and maintain the OVN-Kubernetes network plugin and related components for default internal pod traffic.
 </li>
 </ul>
    </td>
diff --git a/articles/operator-5g-core/quickstart-subscription.md b/articles/operator-5g-core/quickstart-subscription.md
@@ -10,14 +10,10 @@ ms.date: 03/28/2024
 
 # Quickstart: Get Access to Azure Operator 5G Core Preview
 
-Access is currently limited. For now, we're working with customers that have an existing technical partnership with Microsoft and that have targeted specific use cases. In addition to applying for initial access, all requests for Azure Operator 5G Core Previeware required to go through a use case review.
+Access is currently limited. For now, we're working with customers that have an existing technical partnership with Microsoft and that have targeted specific use cases. In addition to applying for initial access, all requests for Azure Operator 5G Core Preview are required to go through a use-case review.
 
-## Apply for access to Azure Operator 5G Core Preview
+**Related content**
 
-[Apply here](https://aka.ms/AO5GC-Activation-Request) for initial access. Contact your account lead for updates on access status.
-
-## Related content
-
-[What is Azure Operator 5G Core?](overview-product.md)
-[Deploy Azure Operator 5G Core](quickstart-deploy-5g-core.md)
-[Deployment order for clusters, network functions, and observability.](concept-deployment-order.md)
+- [What is Azure Operator 5G Core?](overview-product.md)
+- [Deploy Azure Operator 5G Core](quickstart-deploy-5g-core.md)
+- [Deployment order for clusters, network functions, and observability.](concept-deployment-order.md)
diff --git a/articles/trusted-signing/how-to-signing-integrations.md b/articles/trusted-signing/how-to-signing-integrations.md
@@ -144,7 +144,7 @@ You can also use the following tools or platforms to set up signing integrations
 
 - **Azure DevOps task**: To use the Trusted Signing Azure DevOps task, see [Trusted Signing](https://marketplace.visualstudio.com/items?itemName=VisualStudioClient.TrustedSigning&ssr=false#overview) in Visual Studio Marketplace. Complete the instructions for setup.
 
-- **PowerShell for Authenticode**: To use PowerShell for Trusted Signing, see [Trusted Signing 0.3.8](https://www.powershellgallery.com/packages/TrustedSigning/0.3.8) in PowerShell Gallery to install the PowerShell module.
+- **PowerShell for Authenticode**: To use PowerShell for Trusted Signing, see [Trusted Signing](https://www.powershellgallery.com/packages/TrustedSigning/) in PowerShell Gallery to install the PowerShell module.
 
 - **Azure PowerShell - App Control for Business CI policy**: To use Trusted Signing for code integrity (CI) policy signing, follow the instructions in [Sign a new CI policy](./how-to-sign-ci-policy.md) and see [Az.CodeSigning PowerShell Module](/powershell/azure/install-azps-windows).
 
diff --git a/articles/virtual-network/tutorial-filter-network-traffic.md b/articles/virtual-network/tutorial-filter-network-traffic.md
@@ -471,7 +471,7 @@ az network nsg rule create \
 ```
 
 > [!CAUTION]
-> In this article, SSJ (port 22) is exposed to the internet for the VM that is assigned to the **asg-mgmt** application security group.
+> In this article, SSH (port 22) is exposed to the internet for the VM that is assigned to the **asg-mgmt** application security group.
 >
 > For production environments, instead of exposing port 22 to the internet, it's recommended that you connect to Azure resources that you want to manage using a VPN, private network connection, or Azure Bastion.
 >

Original file line number	Diff line number	Diff line change
`@@ -471,7 +471,7 @@ az network nsg rule create \`
`471`	`471`	```
`472`	`472`
`473`	`473`	`> [!CAUTION]`
`474`		`-> In this article, SSJ (port 22) is exposed to the internet for the VM that is assigned to the asg-mgmt application security group.`
	`474`	`+> In this article, SSH (port 22) is exposed to the internet for the VM that is assigned to the asg-mgmt application security group.`
`475`	`475`	`>`
`476`	`476`	`> For production environments, instead of exposing port 22 to the internet, it's recommended that you connect to Azure resources that you want to manage using a VPN, private network connection, or Azure Bastion.`
`477`	`477`	`>`