Merge branch 'main' of https://github.com/MicrosoftDocs/azure-docs-pr into us370875-cli-posh-nat

asudbring · asudbring · commit f0e9ed8f7cea · 2025-03-04T16:40:57.000-06:00
diff --git a/articles/container-apps/manage-secrets.md b/articles/container-apps/manage-secrets.md
@@ -5,7 +5,7 @@ services: container-apps
 author: craigshoemaker
 ms.service: azure-container-apps
 ms.topic: how-to
-ms.date: 02/03/2025
+ms.date: 02/28/2025
 ms.author: cshoe
 ms.custom: devx-track-azurecli, devx-track-azurepowershell, build-2023
 ---
@@ -136,6 +136,9 @@ To grant access to Key Vault secrets, [create an access policy](/azure/key-vault
 
 1. In the *System assigned* tab, set the *Status* to **On**.
 
+> [!NOTE]
+> You can also use a user-assigned managed identity, which can be reused across multiple resources and persists independently of the app lifecycle. To use it, select the *User assigned* tab and choose an existing identity.
+
 1. Select **Save** to enable system assigned managed identity.
 
 1. A popup appears to confirm that you want to enable system assigned managed identity and register your container app with Microsoft Entra ID. Select **Yes**.
@@ -209,7 +212,7 @@ Secrets Key Vault references aren't supported in PowerShell.
 ---
 
 > [!NOTE]
-> If you're using [UDR With Azure Firewall](networking.md#user-defined-routes-udr), you will need to add the `AzureKeyVault` service tag and the *login.microsoft.com* FQDN to the allow list for your firewall. Refer to [configuring UDR with Azure Firewall](networking.md#configuring-udr-with-azure-firewall) to decide which additional service tags you need.
+> If you're using [UDR With Azure Firewall](networking.md#user-defined-routes-udr), you need to add the `AzureKeyVault` service tag and the *login.microsoft.com* FQDN to the allow list for your firewall. Refer to [configuring UDR with Azure Firewall](networking.md#configuring-udr-with-azure-firewall) to decide which additional service tags you need.
 
 #### Key Vault secret URI and secret rotation
 
diff --git a/articles/digital-twins/how-to-manage-twin.md b/articles/digital-twins/how-to-manage-twin.md
diff --git a/articles/digital-twins/media/how-to-manage-twin/console-output-manage-twins.png b/articles/digital-twins/media/how-to-manage-twin/console-output-manage-twins.png
diff --git a/articles/iot-operations/connect-to-cloud/howto-configure-fabric-real-time-intelligence.md b/articles/iot-operations/connect-to-cloud/howto-configure-fabric-real-time-intelligence.md
@@ -62,7 +62,8 @@ Azure Key Vault is the recommended way to sync the connection string to the Kube
     | Host                  | The hostname of the Event Stream Custom Endpoint in the format `*.servicebus.windows.net:9093`. Use the bootstrap server address noted previously. |
     | Authentication method | *SASL* is the currently the only supported authentication method. |
     | SASL type             | Choose *Plain* |
-    | Synced secret name    | Create or select a Key Vault secret where the secret's value is exactly the text **$ConnectionString** (literal string, not an environment variable reference). |
+    | Synced secret name    | Enter a name for the syned secret. A Kubernetes secret with this name will be created on the cluster. |
+    | Username reference of token secret | Create a new or choose an existing Key Vault reference. The secret value must be exactly the text **$ConnectionString** (literal string, not an environment variable reference). |
     | Password reference of token secret | Create a new or choose an existing Key Vault reference. The secret value must be the Custom Endpoint connection string noted earlier. |
 
 1. Select **Apply** to provision the endpoint.
@@ -83,4 +84,4 @@ The advanced settings for this endpoint are identical to the [advanced settings
 
 ## Next steps
 
-To learn more about data flows, see [Create a data flow](howto-create-dataflow.md).
+To learn more about data flows, see [Create a data flow](howto-create-dataflow.md).
diff --git a/articles/reliability/reliability-elastic-san.md b/articles/reliability/reliability-elastic-san.md
@@ -43,7 +43,7 @@ Deploying a ZRS Elastic SAN provides more reliability than an LRS Elastic SAN, b
 
 ### Availability zone migration
 
-To migrate an Elastic SAN on LRS to ZRS, snapshot your Elastic SAN volumes, export them to managed disk snapshots, deploy an Elastic SAN on ZRS, and then create volumes on the SAN on ZRS using those disk snapshots. To learn how to use snapshots (preview), see [Snapshot Azure Elastic SAN volumes (preview)](../storage/elastic-san/elastic-san-snapshots.md).
+To migrate an Elastic SAN on LRS to ZRS, snapshot your Elastic SAN volumes, export them to managed disk snapshots, deploy an Elastic SAN on ZRS, and then create volumes on the SAN on ZRS using those disk snapshots. To learn how to use snapshots, see [Snapshot Azure Elastic SAN volumes](../storage/elastic-san/elastic-san-snapshots.md).
 
 ## Disaster recovery and business continuity
 
@@ -64,4 +64,4 @@ Microsoft and its customers operate under the [Shared Responsibility Model](./co
 ## Next steps
 
 - [Plan for deploying an Elastic SAN](../storage/elastic-san/elastic-san-planning.md)
-- [Snapshot Azure Elastic SAN volumes (preview)](../storage/elastic-san/elastic-san-snapshots.md)
+- [Snapshot Azure Elastic SAN volumes](../storage/elastic-san/elastic-san-snapshots.md)
diff --git a/articles/sentinel/data-connector-connection-rules-reference.md b/articles/sentinel/data-connector-connection-rules-reference.md
@@ -86,7 +86,7 @@ The CCP supports the following authentication types:
 - [Basic](#basic-auth)
 - [APIKey](#apikey)
 - [OAuth2](#oauth2)
-- [Jwt](#jwt)
+- [JWT](#jwt)
 
 > [!NOTE]
 > CCP OAuth2 implementation does not support client certificate credentials.
@@ -215,7 +215,7 @@ OAuth2 `client_credentials` grant type
 }
 ```
 
-#### Jwt
+#### JWT
 
 Example:
 JSON web token (JWT)
diff --git a/articles/storage/elastic-san/elastic-san-introduction.md b/articles/storage/elastic-san/elastic-san-introduction.md
@@ -74,7 +74,7 @@ The status of items in this table might change over time.
 | Private endpoints |	✔️ |
 | Grant network access to specific Azure virtual networks|  ✔️  |
 | Soft delete | ⛔  |
-| Snapshots (preview) | ✔️ |
+| Snapshots | ✔️ |
 
 ## Next steps
 
diff --git a/articles/synapse-analytics/spark/tutorial-spark-pool-filesystem-spec.md b/articles/synapse-analytics/spark/tutorial-spark-pool-filesystem-spec.md
@@ -135,11 +135,13 @@ Run the following code.
 
    > [!NOTE]
    > Update the file URL in this script before running it.
+   > Please ensure you import pandas when using the below code snippet. This is critical for proper handling of access tokens.  
 
    ```PYSPARK
    # Import libraries
    import fsspec
    import os
+   import pandas
    
    # Set variables
    local_file_name = "<local_file_name>"
diff --git a/includes/digital-twins-bulk-delete-note.md b/includes/digital-twins-bulk-delete-note.md
@@ -3,7 +3,7 @@ author: baanders
 description: include file with a note about using the bulk delete API
 ms.service: azure-digital-twins
 ms.topic: include
-ms.date: 10/3/2023
+ms.date: 03/04/2025
 ms.author: baanders
 ---
 
diff --git a/includes/digital-twins-defaultazurecredential-note.md b/includes/digital-twins-defaultazurecredential-note.md
@@ -3,11 +3,11 @@ author: baanders
 description: include file for adding a note about the known issue with DefaultAzureCredential
 ms.service: azure-digital-twins
 ms.topic: include
-ms.date: 2/21/2022
+ms.date: 03/04/2025
 ms.author: baanders
 ---
 
 >[!NOTE]
->There's currently a known issue affecting the `DefaultAzureCredential` wrapper class that may result in an error while authenticating. If you encounter this issue, you can try instantiating `DefaultAzureCredential` with the following optional parameter to resolve it: `new DefaultAzureCredential(new DefaultAzureCredentialOptions { ExcludeSharedTokenCacheCredential = true });`
+>There's currently a known issue affecting the `DefaultAzureCredential` wrapper class that might result in an error while authenticating. If you encounter this issue, you can try instantiating `DefaultAzureCredential` with the following optional parameter to resolve it: `new DefaultAzureCredential(new DefaultAzureCredentialOptions { ExcludeSharedTokenCacheCredential = true });`
 >
 >For more information about this issue, see [Azure Digital Twins known issues](../articles/digital-twins/troubleshoot-known-issues.md#issue-with-default-azure-credential-authentication-on-azureidentity-130).
diff --git a/includes/digital-twins-developer-interfaces.md b/includes/digital-twins-developer-interfaces.md
@@ -1,6 +1,6 @@
 ---
 author: baanders
-description: include file for Azure Digital Twins - developer interfaces for managing instance
+description: Include file for Azure Digital Twins - developer interfaces for managing instance
 ms.service: azure-digital-twins
 ms.topic: include
 ms.date: 02/27/2025
@@ -15,4 +15,3 @@ Other developer interfaces that can be used to complete these operations include
 * [Azure Digital Twins Explorer](../articles/digital-twins/concepts-azure-digital-twins-explorer.md)
 * [REST API](/rest/api/azure-digitaltwins/) calls
 * [Azure CLI](/cli/azure/dt) commands
-
diff --git a/includes/digital-twins-local-credentials-inner.md b/includes/digital-twins-local-credentials-inner.md
@@ -3,10 +3,10 @@ author: baanders
 description: include file for setting up local authentication for DefaultAzureCredential in Azure Digital Twins samples - without intro
 ms.service: azure-digital-twins
 ms.topic: include
-ms.date: 10/22/2020
+ms.date: 03/04/2025
 ms.author: baanders
 ---
 
-With `DefaultAzureCredential`, the sample will search for credentials in your local environment, like an Azure sign-in in a local [Azure CLI](/cli/azure/install-azure-cli) or in Visual Studio or Visual Studio Code. For this reason, you should *sign in to Azure locally* through one of these mechanisms to set up credentials for the sample.
+With `DefaultAzureCredential`, the sample searches for credentials in your local environment, like an Azure sign-in in a local [Azure CLI](/cli/azure/install-azure-cli) or in Visual Studio or Visual Studio Code. For this reason, you should *sign in to Azure locally* through one of these mechanisms to set up credentials for the sample.
 
-If you're using Visual Studio or Visual Studio Code to run code samples, make sure you're [signed in to that editor](/visualstudio/ide/signing-in-to-visual-studio) with the same Azure credentials that you want to use to access your Azure Digital Twins instance. If you're using a local CLI window, run the `az login` command to sign in to your Azure account. After this, when you run your code sample, you should be authenticated automatically. 
+If you're using Visual Studio or Visual Studio Code to run code samples, make sure you're [signed in to that editor](/visualstudio/ide/signing-in-to-visual-studio) with the same Azure credentials that you want to use to access your Azure Digital Twins instance. If you're using a local CLI window, run the `az login` command to sign in to your Azure account. After signing in, when you run your code sample, you should be authenticated automatically. 
diff --git a/includes/digital-twins-local-credentials-outer.md b/includes/digital-twins-local-credentials-outer.md
@@ -3,7 +3,7 @@ author: baanders
 description: include file for setting up local authentication for DefaultAzureCredential in Azure Digital Twins samples - with intro
 ms.service: azure-digital-twins
 ms.topic: include
-ms.date: 10/22/2020
+ms.date: 03/04/2025
 ms.author: baanders
 ---
 
diff --git a/includes/digital-twins-visualization.md b/includes/digital-twins-visualization.md
@@ -1,6 +1,6 @@
 ---
 author: baanders
-description: include file for Azure Digital Twins - visualizing with Azure Digital Twins Explorer
+description: Include file for Azure Digital Twins - visualizing with Azure Digital Twins Explorer
 ms.service: azure-digital-twins
 ms.topic: include
 ms.date: 02/27/2025
