Merge pull request #301296 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/application-gateway/ingress-controller-annotations.md

@@ -27,7 +27,7 @@ For AGIC to observe an ingress resource, the resource *must be annotated* with `
 | [appgw.ingress.kubernetes.io/health-probe-hostname](#custom-health-probe) | `string` | `127.0.0.1` ||
 | [appgw.ingress.kubernetes.io/health-probe-port](#custom-health-probe) | `int32` | `80` ||
 | [appgw.ingress.kubernetes.io/health-probe-path](#custom-health-probe) | `string` | `/` ||
-| [appgw.ingress.kubernetes.io/health-probe-status-code](#custom-health-probe) | `string` | `200-399` ||
+| [appgw.ingress.kubernetes.io/health-probe-status-codes](#custom-health-probe) | `string` | `200-399` ||
 | [appgw.ingress.kubernetes.io/health-probe-interval](#custom-health-probe) | `int32` | `30` (seconds) ||
 | [appgw.ingress.kubernetes.io/health-probe-timeout](#custom-health-probe) | `int32` | `30` (seconds) ||
 | [appgw.ingress.kubernetes.io/health-probe-unhealthy-threshold](#custom-health-probe) | `int32` | `3` ||
@@ -126,7 +126,7 @@ You can [configure Application Gateway](./application-gateway-probe-overview.md)
 - `health-probe-hostname`: This annotation allows a custom hostname on the health probe.
 - `health-probe-port`: This annotation configures a custom port for the health probe.
 - `health-probe-path`: This annotation defines a path for the health probe.
-- `health-probe-status-code`: This annotation allows the health probe to accept different HTTP status codes.
+- `health-probe-status-codes`: This annotation allows the health probe to accept different HTTP status codes.
 - `health-probe-interval`: This annotation defines the interval at which the health probe runs.
 - `health-probe-timeout`: This annotation defines how long the health probe waits for a response before failing the probe.
 - `health-probe-unhealthy-threshold`: This annotation defines how many health probes must fail for the backend to be marked as unhealthy.
@@ -137,7 +137,7 @@ You can [configure Application Gateway](./application-gateway-probe-overview.md)
 appgw.ingress.kubernetes.io/health-probe-hostname: "contoso.com"
 appgw.ingress.kubernetes.io/health-probe-port: 80
 appgw.ingress.kubernetes.io/health-probe-path: "/"
-appgw.ingress.kubernetes.io/health-probe-status-code: "100-599"
+appgw.ingress.kubernetes.io/health-probe-status-codes: "100-599"
 appgw.ingress.kubernetes.io/health-probe-interval: 30
 appgw.ingress.kubernetes.io/health-probe-timeout: 30
 appgw.ingress.kubernetes.io/health-probe-unhealthy-threshold: 2
@@ -155,7 +155,7 @@ metadata:
     appgw.ingress.kubernetes.io/health-probe-hostname: "contoso.com"
     appgw.ingress.kubernetes.io/health-probe-port: 81
     appgw.ingress.kubernetes.io/health-probe-path: "/probepath"
-    appgw.ingress.kubernetes.io/health-probe-status-code: "100-599"
+    appgw.ingress.kubernetes.io/health-probe-status-codes: "100-599"
     appgw.ingress.kubernetes.io/health-probe-interval: 31
     appgw.ingress.kubernetes.io/health-probe-timeout: 31
     appgw.ingress.kubernetes.io/health-probe-unhealthy-threshold: 2

articles/azure-maps/media/power-bi-visual/settings-enable-subprocessing.png

@@ -4,7 +4,7 @@ titleSuffix: Microsoft Azure Maps
 description: This article demonstrates how to manage Azure Maps Power BI visual within your organization.
 author: deniseatmicrosoft
 ms.author: limingchen
-ms.date: 11/29/2021
+ms.date: 06/13/2025
 ms.topic: how-to
 ms.service: azure-maps
 ms.subservice: power-bi-visual
@@ -16,9 +16,38 @@ Power BI provides the ability for designers and tenant administrators to manage
 
 ## Tenant admin options
 
-In PowerBI.com, tenant administrators can turn off the Azure Maps visual for all users. Select **Settings** > **Admin** **Portal** > **Tenant settings**. When disabled, Power BI doesn't display the Azure Maps visual in the visualizations pane.
+Tenant administrators can manage Azure Maps visuals via **Settings** > **Admin** **Portal** > **Tenant settings**. These settings control access and data processing for the entire organization.
 
-:::image type="content" source="media/power-bi-visual/tenant-admin-settings.png" alt-text="Power BI admin portal showing tenant settings for the Azure Maps visual.":::
+### Enable the Azure Maps visual
+
+When enabled, users in the organization can create and view reports that use the Azure Maps visual.
+
+- Microsoft temporarily stores and processes your data for essential services like translating locations into latitudes and longitudes.
+- If Azure Maps services are unavailable in your region, your data can be processed outside your tenant's geographic region, compliance boundary, or national cloud instance.
+
+:::image type="content" source="media/power-bi-visual/settings-enable-visual.png" alt-text="Screenshot of the tenant settings to enable the Azure Maps visual in the Power BI admin portal.":::
+
+### Process data outside your region or boundary
+
+When enabled, data sent to Azure Maps can be processed outside your tenant’s geographic region, compliance boundary, or national cloud instance. This is required because Azure Maps services aren't available in all geographic regions or national clouds.
+
+- Enable this setting to access more capabilities provided by Microsoft Online Services subprocessors.
+- Disabling this setting can limit Azure Maps features if services are unavailable in your compliance region.
+
+:::image type="content" source="media/power-bi-visual/settings-enable-subprocessing.png" alt-text="Screenshot showing that data sent to Azure Maps can be processed outside your tenant’s geographic region, compliance boundary, or national cloud instance.":::
+
+### Allow Microsoft subprocessors to process data
+
+Some Azure Maps features, like the selection tool, can utilize third-party mapping capabilities provided by Microsoft Online Services subprocessors.
+
+- Only essential data is shared with these subprocessors, and is used solely to support Azure Maps services.
+- Data can be stored and processed in the United States or other countries where Microsoft or its subprocessors operate.
+- To enable this setting, "Data sent to Azure Maps can be processed outside your tenant’s geographic region, compliance boundary, or national cloud instance" must also be enabled.
+
+:::image type="content" source="media/power-bi-visual/settings-processed-by-subprocessors.png" alt-text="Screenshot showing that data sent to Azure Maps can be processed by Microsoft Online Services subprocessors.":::
+
+> [!NOTE]
+> Azure Maps and subprocessors don't handle personally identifiable information (PII). The data sent to Azure Maps only includes location-related information, such as coordinates or place names, and doesn't include user identities or report consumer information.
 
 ## Next steps
 

articles/azure-maps/media/power-bi-visual/settings-enable-visual.png

@@ -114,7 +114,7 @@ For frequently asked questions regarding SMB in Azure NetApp Files, see the [Azu
 
 ## Dual protocols
 
-Some organizations have pure Windows or pure UNIX environments (homogenous) in which all data is accessed using only one of the following approaches:
+Some organizations have pure Windows or pure UNIX environments (homogeneous) in which all data is accessed using only one of the following approaches:
 
 * SMB and [NTFS](/windows-server/storage/file-server/ntfs-overview) file security
 * NFS and UNIX file security - mode bits or [NFSv4.x access control lists (ACLs)](https://wiki.linux-nfs.org/wiki/index.php/ACLs)

articles/azure-maps/media/power-bi-visual/settings-processed-by-subprocessors.png

@@ -40,7 +40,7 @@ Along with selecting one or more best-fitting algorithms, you need to consider w
 | Algorithm Category| Use | Learning Type | Algorithms |
 | --- | --- | --- | -- |
 | Classification | Classify people or things into groups | Supervised | Decision trees, Logistic regression, neural networks |
-| Clustering | Dividing a set of examples into homogenous groups | Unsupervised | K-means clustering |
+| Clustering | Dividing a set of examples into homogeneous groups | Unsupervised | K-means clustering |
 | Pattern detection | Identify frequent associations in the data | Unsupervised | Association rules |
 | Regression | Predict numerical outcomes | Supervised | Linear regression, neural networks |
 | Reinforcement | Determine optimal behavior for robots | Reinforcement | Monte Carlo Simulations, DeepMind |

articles/azure-maps/media/power-bi-visual/tenant-admin-settings.png

@@ -362,7 +362,7 @@ This section shows you how to create a Node.js script that adds an enrollment gr
 
 :::zone pivot="programming-language-nodejs"
 
-1. Run the following command in your command prompt. Include the quotes around the command arguments and replace `<connection string>` withe connection string you copied in the previous section, and `<certificate .pem file>` with the path to your certificate `.pem` file. This file represents the public part of a either a root CA X.509 certificate that was previously uploaded and verified with your provisioning service, or an intermediate certificate that was uploaded and verified or had a certificate in its signing chain uploaded and verified.
+1. Run the following command in your command prompt. Include the quotes around the command arguments and replace `<connection string>` with connection string you copied in the previous section, and `<certificate .pem file>` with the path to your certificate `.pem` file. This file represents the public part of a either a root CA X.509 certificate that was previously uploaded and verified with your provisioning service, or an intermediate certificate that was uploaded and verified or had a certificate in its signing chain uploaded and verified.
 
     ```cmd\sh
     node create_enrollment_group.js "<connection string>" "<certificate .pem file>"

articles/azure-maps/power-bi-visual-manage-access.md

@@ -50,7 +50,7 @@ Go through the following steps to help plan an Operator Nexus deployment.
 
 2.  Determine the capacity requirements for each of these workloads, allowing for redundancy for each one.
 
-3.  If your workloads support a split between control-plane and data-plane elements, consider whether to separately design control-plane sites that can control a larger number of more widely distributed data-plane sites. This option is only likely to be attractive for larger deployments. For smaller deployments, or deployments with workloads that don't support separating the control-plane and the data-plane, you're more likely to use a homogenous site architecture where all sites are identical.
+3.  If your workloads support a split between control-plane and data-plane elements, consider whether to separately design control-plane sites that can control a larger number of more widely distributed data-plane sites. This option is only likely to be attractive for larger deployments. For smaller deployments, or deployments with workloads that don't support separating the control-plane and the data-plane, you're more likely to use a homogeneous site architecture where all sites are identical.
 
 
 4.  Plan the distribution of workload instances to determine the number of racks needed in each site type, allowing for the fact that each rack is an Operator Nexus zone. The platform can enforce affinity/anti-affinity rules at the scope of these zones, to ensure workload instances are distributed in such a way as to be resilient to failures of individual servers or racks. See [this article](./howto-virtual-machine-placement-hints.md) for more on affinity/anti-affinity rules. The Operator Nexus Azure Kubernetes Service (NAKS) controller automatically distributes nodes within a cluster across the available servers in a zone as uniformly as possible, within other constraints. As a result, failure of any single server has the minimum impact on the total capacity remaining.