Merge pull request #293894 from MicrosoftDocs/repo_sync_working_branch

v-alje · web-flow · commit 3d902300e725 · 2025-01-31T09:24:24.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/active-directory-b2c/identity-provider-generic-saml-options.md b/articles/active-directory-b2c/identity-provider-generic-saml-options.md
@@ -422,7 +422,7 @@ Upon an application sign-out request, Azure AD B2C attempts to sign out from you
 
 ## Debug SAML protocol
 
-To help configure and debug federation with a SAML identity provider, you can use a browser extension for the SAML protocol, such as [SAML DevTools extension](https://chrome.google.com/webstore/detail/saml-devtools-extension/jndllhgbinhiiddokbeoeepbppdnhhio) for Chrome, [SAML-tracer](https://addons.mozilla.org/es/firefox/addon/saml-tracer/) for FireFox, or [Microsoft Edge or Internet Explorer developer tools](https://techcommunity.microsoft.com/t5/microsoft-sharepoint-blog/gathering-a-saml-token-using-edge-or-ie-developer-tools/ba-p/320957).
+To help configure and debug federation with a SAML identity provider, you can use a browser extension for the SAML protocol, such as [SAML DevTools extension](https://chrome.google.com/webstore/detail/saml-devtools-extension/jndllhgbinhiiddokbeoeepbppdnhhio) for Chrome, [SAML-tracer](https://addons.mozilla.org/es/firefox/addon/saml-tracer/) for Firefox, or [Microsoft Edge or Internet Explorer developer tools](https://techcommunity.microsoft.com/t5/microsoft-sharepoint-blog/gathering-a-saml-token-using-edge-or-ie-developer-tools/ba-p/320957).
 
 Using these tools, you can check the integration between Azure AD B2C and your SAML identity provider. For example:
 
diff --git a/articles/active-directory-b2c/troubleshoot.md b/articles/active-directory-b2c/troubleshoot.md
@@ -165,7 +165,7 @@ Use **Run now** and `https://jwt.ms` to test your policies independently of your
 
 ## Troubleshoot SAML protocol
 
-To help configure and debug the integration with your service provider, you can use a browser extension for the SAML protocol, for example, [SAML DevTools extension](https://chrome.google.com/webstore/detail/saml-devtools-extension/jndllhgbinhiiddokbeoeepbppdnhhio) for Chrome, [SAML-tracer](https://addons.mozilla.org/es/firefox/addon/saml-tracer/) for FireFox, or [Edge or Internet Explorer developer tools](https://techcommunity.microsoft.com/t5/microsoft-sharepoint-blog/gathering-a-saml-token-using-edge-or-ie-developer-tools/ba-p/320957).
+To help configure and debug the integration with your service provider, you can use a browser extension for the SAML protocol, for example, [SAML DevTools extension](https://chrome.google.com/webstore/detail/saml-devtools-extension/jndllhgbinhiiddokbeoeepbppdnhhio) for Chrome, [SAML-tracer](https://addons.mozilla.org/es/firefox/addon/saml-tracer/) for Firefox, or [Edge or Internet Explorer developer tools](https://techcommunity.microsoft.com/t5/microsoft-sharepoint-blog/gathering-a-saml-token-using-edge-or-ie-developer-tools/ba-p/320957).
 
 The following screenshot demonstrates how the SAML DevTools extension presents the SAML request Azure AD B2C sends to the identity provider, and the SAML response.
 
diff --git a/articles/app-service/wordpress-faq.md b/articles/app-service/wordpress-faq.md
@@ -90,7 +90,7 @@ Key tools for debugging and monitoring WordPress sites include:
 - **[SSH Access](configure-linux-open-ssh-session.md?pivots=container-linux)**
 
 ### PhpMyAdmin
-WordPress on App Service utilizes an Azure Database for MySQL flexible server, which is integrated into a VNET. This setup restricts database access to within the VNET. WordPress on App Service includes phpMyAdmin by default. You can access it at: https://`<your-site-link>`/phpmyadmin. 
+WordPress on App Service utilizes an Azure Database for MySQL Flexible Server, which is integrated into a VNET. This setup restricts database access to within the VNET. WordPress on App Service includes phpMyAdmin by default. You can access it at: https://`<your-site-link>`/phpmyadmin. 
  
 If you are using Managed Identities, you can log in to phpMyAdmin by using the value from DATABASE_USERNAME environment variable as the username and the token as the password. To find the token use your Kudu SSH to run the following command: 
  
diff --git a/articles/cloud-shell/faq-troubleshooting.md b/articles/cloud-shell/faq-troubleshooting.md
@@ -27,7 +27,7 @@ the most common key combinations:
 
 - Windows: <kbd>Ctrl</kbd>+<kbd>c</kbd> to copy and <kbd>CTRL</kbd>+<kbd>Shift</kbd>+<kbd>v</kbd> or
   <kbd>Shift</kbd>+<kbd>Insert</kbd> to paste.
-  - FireFox might not support clipboard permissions properly.
+  - Firefox might not support clipboard permissions properly.
 - macOS: <kbd>Cmd</kbd>+<kbd>c</kbd> to copy and <kbd>Cmd</kbd>+<kbd>v</kbd> to paste.
 - Linux: <kbd>CTRL</kbd>+<kbd>c</kbd> to copy and <kbd>CTRL</kbd>+<kbd>Shift</kbd>+<kbd>v</kbd> to
   paste.
diff --git a/articles/cloud-shell/new-ui-shell-window.md b/articles/cloud-shell/new-ui-shell-window.md
@@ -137,7 +137,7 @@ When you select the **Close** button, the Cloud Shell session is terminated.
 
 - Windows: <kbd>Ctrl</kbd>+<kbd>c</kbd> to copy is supported but use
   <kbd>Shift</kbd>+<kbd>Insert</kbd> to paste.
-  - The FireFox browser might not support clipboard permissions properly.
+  - The Firefox browser might not support clipboard permissions properly.
 - macOS: <kbd>Cmd</kbd>+<kbd>c</kbd> to copy and <kbd>Cmd</kbd>+<kbd>v</kbd> to paste.
 - Linux: <kbd>Ctrl</kbd>+<kbd>c</kbd> to copy and <kbd>Ctrl</kbd>+<kbd>Shift</kbd>+<kbd>v</kbd> to paste.
 
diff --git a/articles/cloud-shell/using-the-shell-window.md b/articles/cloud-shell/using-the-shell-window.md
@@ -106,7 +106,7 @@ select restore.
 
 - Windows: <kbd>Ctrl</kbd>-<kbd>C</kbd> to copy is supported but use
   <kbd>Shift</kbd>-<kbd>Insert</kbd> to paste.
-  - FireFox and Internet Explorer may not support clipboard permissions properly.
+  - Firefox and Internet Explorer may not support clipboard permissions properly.
 - macOS: <kbd>Cmd</kbd>-<kbd>C</kbd> to copy and <kbd>Cmd</kbd>-<kbd>V</kbd> to paste.
 - Linux: <kbd>CTRL</kbd>-<kbd>C</kbd> to copy and <kbd>CTRL</kbd>-<kbd>SHIFT</kbd>-<kbd>V</kbd> to paste.
 
diff --git a/articles/databox-online/azure-stack-edge-gpu-configure-gpu-modules.md b/articles/databox-online/azure-stack-edge-gpu-configure-gpu-modules.md
@@ -97,7 +97,7 @@ To configure a module to use the GPU on your Azure Stack Edge Pro device to run
 
        ![Configure module to use GPU 11](media/azure-stack-edge-gpu-configure-gpu-modules/configure-gpu-7.png)
 
-       For more information on environment variables that you can use with the NVIDIA GPU, go to [nVidia container runtime](https://github.com/NVIDIA/nvidia-container-runtime#environment-variables-oci-spec).
+       For more information on environment variables that you can use with the NVIDIA GPU, go to [NVIDIA container runtime](https://github.com/NVIDIA/nvidia-container-runtime#environment-variables-oci-spec).
 
     > [!NOTE]
     > A module can use one, both or no GPUs.
diff --git a/articles/databox-online/azure-stack-edge-gpu-technical-specifications-compliance.md b/articles/databox-online/azure-stack-edge-gpu-technical-specifications-compliance.md
@@ -34,7 +34,7 @@ A Graphics Processing Unit (GPU) is included on every Azure Stack Edge Pro devic
 
 | Specification           | Value                  |
 |-------------------------|----------------------------|
-| GPU   | One or two nVidia T4 GPUs <br> For more information, see [NVIDIA T4](https://www.nvidia.com/en-us/data-center/tesla-t4/).|
+| GPU   | One or two NVIDIA T4 GPUs <br> For more information, see [NVIDIA T4](https://www.nvidia.com/en-us/data-center/tesla-t4/).|
 
 
 ## Power supply unit specifications
diff --git a/articles/databox-online/azure-stack-edge-pro-r-technical-specifications-compliance.md b/articles/databox-online/azure-stack-edge-pro-r-technical-specifications-compliance.md
@@ -33,7 +33,7 @@ A Graphics Processing Unit (GPU) is included on every device that enables Kubern
 
 | Specification           | Value                      |
 |-------------------------|----------------------------|
-| GPU   | One nVidia T4 GPU <br> For more information, see [NVIDIA T4](https://www.nvidia.com/en-us/data-center/tesla-t4/). | 
+| GPU   | One NVIDIA T4 GPU <br> For more information, see [NVIDIA T4](https://www.nvidia.com/en-us/data-center/tesla-t4/). | 
 
 ## Power supply unit specifications
 
diff --git a/articles/hdinsight/hdinsight-linux-ambari-ssh-tunnel.md b/articles/hdinsight/hdinsight-linux-ambari-ssh-tunnel.md
@@ -108,7 +108,7 @@ Once the command finishes, traffic sent to port 9876 on the local computer is ro
 ## Use the tunnel from your browser
 
 > [!IMPORTANT]  
-> The steps in this section use the Mozilla FireFox browser, as it provides the same proxy settings across all platforms. Other modern browsers, such as Google Chrome, may require an extension such as FoxyProxy to work with the tunnel.
+> The steps in this section use the Mozilla Firefox browser, as it provides the same proxy settings across all platforms. Other modern browsers, such as Google Chrome, may require an extension such as FoxyProxy to work with the tunnel.
 
 1. Configure the browser to use **localhost** and the port you used when creating the tunnel as a **SOCKS v5** proxy. Here's what the Firefox settings look like. If you used a different port than 9876, change the port to the one you used:
 
diff --git a/articles/hdinsight/hdinsight-release-notes-archive.md b/articles/hdinsight/hdinsight-release-notes-archive.md
@@ -1109,7 +1109,7 @@ HDI Hive 3.1 version is upgraded to OSS Hive 3.1.2. This version has all fixes a
 | LLAP status service driver might get stuck with wrong Yarn app ID|[HIVE-21866](https://issues.apache.org/jira/browse/HIVE-21866)|
 | OperationManager.queryIdOperation doesn't  properly clean up multiple queryIds|[HIVE-22275](https://issues.apache.org/jira/browse/HIVE-22275)|
 | Bringing a node manager down blocks restart of LLAP service|[HIVE-22219](https://issues.apache.org/jira/browse/HIVE-22219)|
-| StackOverflowError when drop lots of partitions|[HIVE-15956](https://issues.apache.org/jira/browse/HIVE-15956)|
+| Stack OverflowError when drop lots of partitions|[HIVE-15956](https://issues.apache.org/jira/browse/HIVE-15956)|
 | Access check is failed when a temporary directory is removed|[HIVE-22273](https://issues.apache.org/jira/browse/HIVE-22273)|
 | Fix wrong results/ArrayOutOfBound exception in left outer map joins on specific boundary conditions|[HIVE-22120](https://issues.apache.org/jira/browse/HIVE-22120)|
 | Remove distribution management tag from pom.xml|[HIVE-19667](https://issues.apache.org/jira/browse/HIVE-19667)|
diff --git a/articles/synapse-analytics/security/workspace-data-exfiltration-protection.md b/articles/synapse-analytics/security/workspace-data-exfiltration-protection.md
@@ -14,7 +14,7 @@ This article will explain data exfiltration protection in Azure Synapse Analytic
 
 ## Securing data egress from Synapse workspaces
 Azure Synapse Analytics workspaces support enabling data exfiltration protection for workspaces. With exfiltration protection, you can guard against malicious insiders accessing your Azure resources and exfiltrating sensitive data to locations outside of your organization’s scope. 
-At the time of workspace creation, you can choose to configure the workspace with a managed virtual network and additional protection against data exfiltration. When a workspace is created with a [managed virtual network](./synapse-workspace-managed-vnet.md), Data integration and Spark resources are deployed in the managed virtual network. The workspace’s dedicated SQL pools and serverless SQL pools have multi-tenant capabilities and as such, need to exist outside the managed virtual network. For workspaces with data exfiltration protection, resources within the managed virtual network always communicate over [managed private endpoints](./synapse-workspace-managed-private-endpoints.md). When data exfiltration protection is enabled, Synapse SQL resources can connect to and query any authorized Azure Storage using OPENROWSETS or EXTERNAL TABLE, since the ingress traffic is not controlled by the data exfiltration protection. However, the egress traffic via [CREATE EXTERNAL TABLE AS SELECT](/sql/t-sql/statements/create-external-table-as-select-transact-sql?view=azure-sqldw-latest&preserve-view=true) will be controlled by the data exfiltration protection.
+At the time of workspace creation, you can choose to configure the workspace with a managed virtual network and additional protection against data exfiltration. When a workspace is created with a [managed virtual network](./synapse-workspace-managed-vnet.md), Data integration and Spark resources are deployed in the managed virtual network. The workspace’s dedicated SQL pools and serverless SQL pools have multi-tenant capabilities and as such, need to exist outside the managed virtual network. For workspaces with data exfiltration protection, resources within the managed virtual network always communicate over [managed private endpoints](./synapse-workspace-managed-private-endpoints.md). When data exfiltration protection is enabled, Synapse SQL resources can connect to and query any authorized Azure Storage using OPENROWSETS or EXTERNAL TABLE, since the ingress traffic is not controlled by the data exfiltration protection. However, the egress traffic, for example [CREATE EXTERNAL TABLE AS SELECT](/sql/t-sql/statements/create-external-table-as-select-transact-sql?view=azure-sqldw-latest&preserve-view=true) or using ERRORFILE argument in [COPY INTO](/sql/t-sql/statements/copy-into-transact-sql?view=azure-sqldw-latest&preserve-view=true) command to output data to the external storage account will be controlled by the data exfiltration protection. Therefore, it also requires to create the managed private endpoint for the target storage account to unblock the egress traffic to it. 
 
 > [!Note]
 > You cannot change the workspace configuration for managed virtual network and data exfiltration protection after the workspace is created.
diff --git a/articles/synapse-analytics/troubleshoot/troubleshoot-synapse-studio.md b/articles/synapse-analytics/troubleshoot/troubleshoot-synapse-studio.md
@@ -53,7 +53,7 @@ Running the query with "serverless SQL pool" gives you the "Failed to establish
 ### Troubleshooting steps
 
 > [!NOTE] 
->    The following troubleshooting steps are for Chromium Edge and Chrome. You may use other browsers (such as FireFox) with the same troubleshooting steps, but the "Developer Tool" window may have different layout from the screenshots in this TSG. If possible, DO NOT use classical Edge for troubleshooting, as it may show inaccurate information in certain situation.
+>    The following troubleshooting steps are for Chromium Edge and Chrome. You may use other browsers (such as Firefox) with the same troubleshooting steps, but the "Developer Tool" window may have different layout from the screenshots in this TSG. If possible, DO NOT use classical Edge for troubleshooting, as it may show inaccurate information in certain situation.
 
 Open the "Diagnostic Info" panel, select the "Download Diagnostic" button. Keep the downloaded information for error reporting. You can instead, copy the "Session ID" and attach it when opening the support ticket.
 
diff --git a/articles/virtual-wan/point-to-site-vpn-client-cert-mac.md b/articles/virtual-wan/point-to-site-vpn-client-cert-mac.md
@@ -33,7 +33,7 @@ The following example uses **TunnelBlick**.
 
 ##  <a name="OpenVPN-iOS"></a>OpenVPN Client - iOS steps
 
-The following example uses **OpenVPN Connect** from the App store.
+The following example uses **OpenVPN Connect** from the App Store.
 
 [!INCLUDE [OpenVPN iOS](../../includes/vpn-gateway-vwan-config-openvpn-ios.md)]
 
diff --git a/articles/virtual-wan/point-to-site-vpn-client-certificate-openvpn-ios.md b/articles/virtual-wan/point-to-site-vpn-client-certificate-openvpn-ios.md
@@ -23,7 +23,7 @@ For information about working with certificates, see [Generate and export certif
 
 ## Configure the OpenVPN client
 
-The following example uses **OpenVPN Connect** from the App store.
+The following example uses **OpenVPN Connect** from the App Store.
 
 [!INCLUDE [OpenVPN iOS](../../includes/vpn-gateway-vwan-config-openvpn-ios.md)]
 
diff --git a/articles/vpn-gateway/point-to-site-vpn-client-certificate-openvpn-ios.md b/articles/vpn-gateway/point-to-site-vpn-client-certificate-openvpn-ios.md
@@ -51,7 +51,7 @@ For information about working with certificates, see [Point-to site: Generate ce
 
 ## Configure the OpenVPN client
 
-The following example uses **OpenVPN Connect** from the App store.
+The following example uses **OpenVPN Connect** from the App Store.
 
 [!INCLUDE [OpenVPN iOS](../../includes/vpn-gateway-vwan-config-openvpn-ios.md)]
 
diff --git a/includes/azure-stack-edge-gateway-supported-browsers.md b/includes/azure-stack-edge-gateway-supported-browsers.md
@@ -13,5 +13,5 @@ Here is a list of the browsers supported for the local web UI for the virtual de
 |Google Chrome   |Latest version         |        |
 |Microsoft Edge    | Latest version        |         |
 |Internet Explorer     | Latest version        | If enhanced security features are enabled, you may not be able to access local web UI pages. Disable enhanced security, and restart your browser.|
-|FireFox    |Latest version         |         |
+|Firefox    |Latest version         |         |
 |Safari on Mac    |Latest version         |         |
diff --git a/includes/data-box-edge-gateway-supported-browsers.md b/includes/data-box-edge-gateway-supported-browsers.md
@@ -13,4 +13,4 @@ The following list of browsers are supported for the virtual device's local web
 |Google Chrome   |Latest version         |         |
 |Microsoft Edge    | Latest version        |         |
 |Internet Explorer     | Latest version        |If Enhanced Security features are enabled, you might not be able to access local web UI pages. Disable enhanced security, and restart your browser. |
-|FireFox    |Latest version         |         |
+|Firefox    |Latest version         |         |
diff --git a/includes/data-box-supported-web-browsers.md b/includes/data-box-supported-web-browsers.md
@@ -12,6 +12,6 @@ Here is a list of web browsers supported for the local web UI.
 | --- | --- | --- |
 | Google Chrome |Latest version |Tested with Chrome|
 | Microsoft Edge |Latest version | |
-| FireFox | Latest version | Tested with FireFox|
+| Firefox | Latest version | Tested with Firefox|
 | Internet Explorer |Latest version |If you cannot sign in, check if cookies and JavaScript are enabled. To enable the UI access, add the device IP to **Privacy Actions** so that the device can access cookies. |
 
diff --git a/includes/vpn-gateway-vwan-config-openvpn-ios.md b/includes/vpn-gateway-vwan-config-openvpn-ios.md
@@ -14,7 +14,7 @@
 
 [!INCLUDE [OpenVPN client version 2.6 not supported](./vpn-gateway-vwan-open-vpn-client-version-unsupported.md)]
 
-1. Install the OpenVPN client (version 2.4 or higher) from the App store. Version 2.6 is not yet supported.
+1. Install the OpenVPN client (version 2.4 or higher) from the App Store. Version 2.6 is not yet supported.
 1. If you haven't already done so, download the VPN client profile package from the Azure portal.
 1. Unzip the profile. Open the vpnconfig.ovpn configuration file from the OpenVPN folder in a text editor.
 1. Fill in the P2S client certificate section with the P2S client certificate public key in base64. In a PEM formatted certificate, you can open the .cer file and copy over the base64 key between the certificate headers.
