Merge pull request #301079 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-maps/media/power-bi-visual/layer-position.png

@@ -84,9 +84,33 @@ The general layer section of the **Format** pane are common settings that apply
 
 | Setting        | Description                            |
 |----------------|----------------------------------------|
-| Unselected transparency | The transparency of shapes that aren't selected, when one or more shapes are selected.  |
-| Min data value | The minimum value of the input data to scale against. Good for clipping outliers.  |
-| Max data value | The maximum value of the input data to scale against. Good for clipping outliers.  |
+| Unselected transparency | The transparency of shapes that aren't selected, when one or more shapes are selected. |
+| Min data value | The minimum value of the input data to scale against. Good for clipping outliers. |
+| Max data value | The maximum value of the input data to scale against. Good for clipping outliers. |
+
+## Layer positions
+
+In the Azure Maps visual, certain layers are fixed, meaning they're set at a predefined level and can't be repositioned. Other layers are adjustable, giving users the flexibility to choose from three positioning options: "Above Labels," "Below Labels," or "Below Roads."
+
+:::image type="content" source="media/power-bi-visual/layer-position.png" alt-text="a screenshot showing the layer position drop-down list.":::
+
+Within each Layer position, the order of layers remains consistent. For instance, the 3D bar chart layer always appears above the bubble layer due to its higher layer order, regardless of whether they're placed in "Below Labels" or "Above Labels."
+
+## Layer order
+
+The following table outlines the layer order from top to bottom along with their respective layer position types. Layers marked as "Adjustable" can have their position changed using the Layer position dropdown, as shown in the previous screenshot. Layers marked as "Fixed" don't offer this option.
+
+| Layer Name           | Layer Order | Position type | Description                                           |
+|----------------------|-------------|---------------|-------------------------------------------------------|
+| Category Labels      | 1           | Fixed         |  The Category Labels is fixed as the top-most layer. You can consider this layer as "fixed" at the highest position. |
+| Selection Tools      | 2           | Fixed         |The Selection tool layer is fixed as the second-highest layer, overlaying all other map layers. "Fixed" means it remains in the second level.|
+| 3D Bar chart Layer   | 3           | Adjustable    |                                                       |
+| Pie chart Layer<br>Bubble Layer<br>Cluster Bubble Layer<br>Path Layer | 4 | Adjustable | These layers share the same "Layer position" as the bubble layer, and their relative order within this group remains fixed. |
+| Heat Map Layer       | 5           | Adjustable    |                                                       |
+| Reference Layer      | 6           | Fixed         |The Reference Layer is fixed at "Below labels".   |
+| Filled Map Layer     | 7           | Adjustable    |                                                       |
+| Tile Layer           | 8           | Adjustable    |                                                       |
+| Map Tiles            | 9           | Fixed         |The Map Tiles layer is fixed as the bottom-most map layer. It's the base map layer of the Azure Maps visual.|
 
 ## Next steps
 

articles/azure-maps/power-bi-visual-understanding-layers.md

@@ -6,7 +6,7 @@ author: craigshoemaker
 ms.service: azure-container-apps
 ms.custom: devx-track-azurecli
 ms.topic: tutorial
-ms.date: 03/20/2025
+ms.date: 06/09/2025
 ms.author: cshoe
 ---
 
@@ -33,7 +33,7 @@ In this tutorial, you learn how to:
 
 ## Set up the environment
 
-The following commands help you define  variables and ensure your Container Apps extension is up to date.
+The following commands define environment variables and ensure your Container Apps extension is up to date.
 
 1. Sign in to the Azure CLI.
 
@@ -291,7 +291,7 @@ Next, create a storage account and establish a file share to mount to the contai
 
     ---
 
-    The storage account key is required to create the storage link in your Container Apps environment.
+    The storage account key is required to create the storage link in your Container Apps environment. Container Apps does not support identity-based access to Azure file shares.
 
 1. Define the storage mount name.
 

articles/container-apps/storage-mounts-azure-files.md

@@ -51,7 +51,7 @@ The following table lists the built-in roles and the actions/permissions that ea
 |Role|Actions|
 |--|--|
 |Synapse Administrator|workspaces/read</br>workspaces/roleAssignments/write, delete</br>workspaces/managedPrivateEndpoint/write, delete</br>workspaces/bigDataPool/useCompute/action</br>workspaces/bigDataPool/viewLogs/action</br>workspaces/scopePool/useCompute/action</br>workspaces/scopePool/viewLogs/action</br>workspaces/integrationRuntime/useCompute/action</br>workspaces/integrationRuntime/viewLogs/action</br>workspaces/artifacts/read</br>workspaces/notebooks/write</br>workspaces/sparkJobDefinitions/write, delete</br>workspaces/scopeJobDefinitions/write, delete</br>workspaces/sqlScripts/write, delete</br>workspaces/dataFlows/write, delete</br>workspaces/dataMappers/write, delete</br>workspaces/pipelines/write, delete</br>workspaces/triggers/write, delete</br>workspaces/datasets/write, delete</br>workspaces/linkedServices/write, delete</br>workspaces/credentials/write, delete</br>workspaces/notebooks/delete</br>workspaces/cancelPipelineRun/action</br>workspaces/notebooksViewOutputs/action</br>workspaces/pipelinesViewOutputs/action</br>workspaces/linkedServicesUseSecret/action</br>workspaces/credentialsUseSecret/action</br>workspaces/libraries/write, delete</br>workspaces/kQLScripts/write, delete</br>workspaces/sparkConfigurations/write, delete</br>workspaces/synapseLinkConnections/read, write, delete</br>workspaces/synapseLinkConnections/useCompute/action|
-|Synapse Apache Spark Administrator|workspaces/read</br>orkspaces/bigDataPoolUseCompute/action</br>orkspaces/bigDataPoolViewLogs/action</br>orkspaces/artifacts/read</br>orkspaces/notebooks/write, delete</br>orkspaces/sparkJobDefinitions/write, delete</br>orkspaces/linkedServices/write, delete</br>orkspaces/credentials/write, delete</br>orkspaces/libraries/write, delete</br>orkspaces/notebooksViewOutputs/action</br>|
+|Synapse Apache Spark Administrator|workspaces/read</br>workspaces/bigDataPoolUseCompute/action</br>workspaces/bigDataPoolViewLogs/action</br>workspaces/artifacts/read</br>workspaces/notebooks/write, delete</br>workspaces/sparkJobDefinitions/write, delete</br>workspaces/linkedServices/write, delete</br>workspaces/credentials/write, delete</br>workspaces/libraries/write, delete</br>workspaces/notebooksViewOutputs/action</br>|
 |Synapse SQL Administrator|workspaces/read</br>workspaces/artifacts/read</br>workspaces/sqlScripts/write, delete</br>workspaces/linkedServices/write, delete</br>workspaces/credentials/write, delete|
 |Synapse Scope Administrator|workspaces/read</br>workspaces/scopePoolUseCompute/action</br>workspaces/scopePoolViewLogs/action</br>workspaces/linkedServices/write, delete</br>workspaces/credentials/write, delete</br>workspaces/scopeJobDefinitions/write, delete|
 |Synapse Private Endpoint Manager|workspaces/read</br>workspaces/managedPrivateEndpoint/write, delete</br>workspaces/linkedServices/write, delete</br>workspaces/credentials/write, delete|