Merge branch 'main' of https://github.com/MicrosoftDocs/azure-docs-pr into patricka-block-storage-fix

Author: PatAltimore

articles/ai-services/immersive-reader/how-to-create-immersive-reader.md

@@ -68,12 +68,12 @@ helm install ingress-nginx ingress-nginx/ingress-nginx `
   --set controller.service.externalTrafficPolicy=Local
 ```
 
-> [!NOTE]
-> In this tutorial, "service.beta.kubernetes.io/azure-load-balancer-health-probe-request-path" is being set to "/healthz". This means if the response code of the requests to "/healthz" is not "200", the whole ingress controller will be down. You can modify the value to other URI in your own scenario. You cannot delete this part or unset the value, or the ingress controller will still be down.
-> The package "ingress-nginx" used in this tutorial, which is provided by [Kubernetes official](https://github.com/kubernetes/ingress-nginx), will always return "200" response code if requesting "/healthz", as it is designed as "[default backend](https://kubernetes.github.io/ingress-nginx/user-guide/default-backend/)" for users to have a quick start, unless it is being overwritten by ingress rules.
-
 ---
 
+> [!NOTE]
+> In this tutorial, `service.beta.kubernetes.io/azure-load-balancer-health-probe-request-path` is being set to `/healthz`. This means if the response code of the requests to `/healthz` is not `200`, the entire ingress controller will be down. You can modify the value to other URI in your own scenario. You cannot delete this part or unset the value, or the ingress controller will still be down.
+> The package `ingress-nginx` used in this tutorial, which is provided by [Kubernetes official](https://github.com/kubernetes/ingress-nginx), will always return `200` response code if requesting `/healthz`, as it is designed as [default backend](https://kubernetes.github.io/ingress-nginx/user-guide/default-backend/) for users to have a quick start, unless it is being overwritten by ingress rules.
+
 ## Customized configuration
 
 As an alternative to the basic configuration presented in the above section, the next set of steps will show how to deploy a customized ingress controller. You'll have the option of using an internal static IP address, or using a dynamic public IP address.

articles/aks/ingress-basic.md

@@ -90,17 +90,17 @@ Because most Azure Cache for Redis clients assume that a password and access key
 
 ### Microsoft Entra Client Workflow
 
-1. Configure your client application to acquire a Microsoft Entra token for scope,  `https://redis.azure.com/.default` or `acca5fbb-b7e4-4009-81f1-37e38fd66d78/.default`, using the [Microsoft Authentication Library (MSAL)](/azure/active-directory/develop/msal-overview).
+1. Configure your client application to acquire a Microsoft Entra token for scope, `https://redis.azure.com/.default` or `acca5fbb-b7e4-4009-81f1-37e38fd66d78/.default`, using the [Microsoft Authentication Library (MSAL)](/azure/active-directory/develop/msal-overview).
 
-1. Update your Redis connection logic to use following `UserName` and `Password`:
+1. Update your Redis connection logic to use following `User` and `Password`:
 
-    `UserName` = Object ID of your managed identity or service principal
-    `Password` = Microsoft Entra token that you acquired using MSAL
+   - `User` = Object ID of your managed identity or service principal
+   - `Password` = Microsoft Entra token that you acquired using MSAL
 
 1. Ensure that your client executes a Redis [AUTH command](https://redis.io/commands/auth/) automatically before your Microsoft Entra token expires using:
 
-    `UserName` = Object ID of your managed identity or service principal
-    `Password` = Microsoft Entra token refreshed periodically
+   - `User` = Object ID of your managed identity or service principal
+   - `Password` = Microsoft Entra token refreshed periodically
 
 ### Client library support
 

articles/azure-cache-for-redis/cache-azure-active-directory-for-authentication.md

@@ -3,7 +3,7 @@ title: Manage instances in Durable Functions - Azure
 description: Learn how to manage instances in the Durable Functions extension for Azure Functions.
 author: cgillum
 ms.topic: conceptual
-ms.date: 12/07/2022
+ms.date: 02/13/2024
 ms.author: azfuncdf
 ms.devlang: csharp
 # ms.devlang: csharp, java, javascript, python
@@ -1109,10 +1109,10 @@ Functions can send instances of these objects to external systems to monitor or
 public static void SendInstanceInfo(
     [ActivityTrigger] IDurableActivityContext ctx,
     [DurableClient] IDurableOrchestrationClient client,
-    [DocumentDB(
+    [CosmosDB(
         databaseName: "MonitorDB",
-        collectionName: "HttpManagementPayloads",
-        ConnectionStringSetting = "CosmosDBConnection")]out dynamic document)
+        containerName: "HttpManagementPayloads",
+        Connection = "CosmosDBConnectionSetting")]out dynamic document)
 {
     HttpManagementPayload payload = client.CreateHttpManagementPayload(ctx.InstanceId);
 

articles/azure-functions/durable/durable-functions-instance-management.md

@@ -1,7 +1,7 @@
 ---
 title: Connect Azure Functions to Azure Cosmos DB using Visual Studio Code
 description: Learn how to connect Azure Functions to an Azure Cosmos DB account by adding an output binding to your Visual Studio Code project.
-ms.date: 02/09/2023
+ms.date: 02/13/2024
 ms.topic: quickstart
 zone_pivot_groups: programming-languages-set-functions-temp
 ms.devlang: csharp
@@ -76,10 +76,10 @@ In the [previous quickstart article](./create-first-function-vs-code-csharp.md),
 
     |Prompt| Selection|
     |--|--|
-    |**Enter new app setting name**| Type `CosmosDbConnectionString`.|
-    |**Enter value for "CosmosDbConnectionString"**| Paste the connection string of your Azure Cosmos DB account you copied.|
+    |**Enter new app setting name**| Type `CosmosDbConnectionSetting`.|
+    |**Enter value for "CosmosDbConnectionSetting"**| Paste the connection string of your Azure Cosmos DB account you copied. You can also configure [Microsoft Entra identity](./functions-bindings-cosmosdb-v2-trigger.md#connections) as an alternative.|
 
-    This creates an application setting named connection `CosmosDbConnectionString` in your function app in Azure. Now, you can download this setting to your local.settings.json file.
+    This creates an application setting named connection `CosmosDbConnectionSetting` in your function app in Azure. Now, you can download this setting to your local.settings.json file.
 
 1. Press <kbd>F1</kbd> again to open the command palette, then search for and run the command `Azure Functions: Download Remote Settings...`. 
 
@@ -97,11 +97,11 @@ Except for HTTP and timer triggers, bindings are implemented as extension packag
 
 # [Isolated worker model](#tab/isolated-process)
 ```command
-dotnet add package Microsoft.Azure.Functions.Worker.Extensions.CosmosDB --version 3.0.9
+dotnet add package Microsoft.Azure.Functions.Worker.Extensions.CosmosDB
 ```
 # [In-process model](#tab/in-process)
 ```command
-dotnet add package Microsoft.Azure.WebJobs.Extensions.CosmosDB --version 3.0.10
+dotnet add package Microsoft.Azure.WebJobs.Extensions.CosmosDB
 ```
 ---
 ::: zone-end
@@ -141,7 +141,7 @@ The `documentsOut` parameter is an `IAsyncCollector<T>` type, which represents a
 
 ---
 
-Specific attributes specify the name of the container and the name of its parent database. The connection string for your Azure Cosmos DB account is set by the `CosmosDbConnectionString`.
+Specific attributes specify the name of the container and the name of its parent database. The connection string for your Azure Cosmos DB account is set by the `CosmosDbConnectionSetting`.
 
 ::: zone-end
 
@@ -159,7 +159,7 @@ To create a binding, right-click (Ctrl+select on macOS) the *function.json* file
 | **The Azure Cosmos DB database where data will be written** | `my-database` | The name of the Azure Cosmos DB database containing the target container. |
 | **Database collection where data will be written** | `my-container` | The name of the Azure Cosmos DB container where the JSON documents will be written. |
 | **If true, creates the Azure Cosmos DB database and collection** | `false` | The target database and container already exist. |
-| **Select setting from "local.setting.json"** | `CosmosDbConnectionString` | The name of an application setting that contains the connection string for the Azure Cosmos DB account. |
+| **Select setting from "local.setting.json"** | `CosmosDbConnectionSetting` | The name of an application setting that contains the connection string for the Azure Cosmos DB account. |
 | **Partition key (optional)** | *leave blank* | Only required when the output binding creates the container. |
 | **Collection throughput (optional)** | *leave blank* | Only required when the output binding creates the container. |
 
@@ -171,9 +171,9 @@ A binding is added to the `bindings` array in your *function.json*, which should
     "direction": "out",
     "name": "outputDocument",
     "databaseName": "my-database",
-    "collectionName": "my-container",
+    "containerName": "my-container",
     "createIfNotExists": "false",
-    "connectionStringSetting": "CosmosDbConnectionString"
+    "connection": "CosmosDbConnectionSetting"
 }
 ```
 
@@ -197,7 +197,7 @@ To create a binding, right-select (Ctrl+select on macOS) the *function.json* fil
 | **The Azure Cosmos DB database where data will be written** | `my-database` | The name of the Azure Cosmos DB database containing the target container. |
 | **Database collection where data will be written** | `my-container` | The name of the Azure Cosmos DB container where the JSON documents will be written. |
 | **If true, creates the Azure Cosmos DB database and collection** | `false` | The target database and container already exist. |
-| **Select setting from "local.setting.json"** | `CosmosDbConnectionString` | The name of an application setting that contains the connection string for the Azure Cosmos DB account. |
+| **Select setting from "local.setting.json"** | `CosmosDbConnectionSetting` | The name of an application setting that contains the connection string for the Azure Cosmos DB account. |
 | **Partition key (optional)** | *leave blank* | Only required when the output binding creates the container. |
 | **Collection throughput (optional)** | *leave blank* | Only required when the output binding creates the container. |
 
@@ -209,9 +209,9 @@ A binding is added to the `bindings` array in your *function.json*, which should
     "direction": "out",
     "name": "outputDocument",
     "databaseName": "my-database",
-    "collectionName": "my-container",
+    "containerName": "my-container",
     "createIfNotExists": "false",
-    "connectionStringSetting": "CosmosDbConnectionString"
+    "connection": "CosmosDbConnectionSetting"
 }
 ```
 
@@ -221,10 +221,10 @@ Binding attributes are defined directly in the *function_app.py* file. You use t
 
 ```python
 @app.cosmos_db_output(arg_name="outputDocument", database_name="my-database", 
-    collection_name="my-container", connection_string_setting="CosmosDbConnectionString")
+    container_name="my-container", connection="CosmosDbConnectionSetting")
 ```
 
-In this code, `arg_name` identifies the binding parameter referenced in your code, `database_name` and `collection_name` are the database and collection names that the binding writes to, and `connection_string_setting` is the name of an application setting that contains the connection string for the Storage account, which is in the CosmosDbConnectionString setting in the *local.settings.json* file.
+In this code, `arg_name` identifies the binding parameter referenced in your code, `database_name` and `container_name` are the database and collection names that the binding writes to, and `connection` is the name of an application setting that contains the connection string for the Azure Cosmos DB account, which is in the `CosmosDbConnectionSetting` setting in the *local.settings.json* file.
 
 ---
 
@@ -265,8 +265,8 @@ public static async Task<IActionResult> Run(
     [HttpTrigger(AuthorizationLevel.Anonymous, "get", "post", Route = null)] HttpRequest req,
     [CosmosDB(
         databaseName: "my-database",
-        collectionName: "my-container",
-        ConnectionStringSetting = "CosmosDbConnectionString")]IAsyncCollector<dynamic> documentsOut,
+        containerName: "my-container",
+        Connection = "CosmosDbConnectionSetting")]IAsyncCollector<dynamic> documentsOut,
     ILogger log)
 {
     log.LogInformation("C# HTTP trigger function processed a request.");
@@ -392,7 +392,7 @@ app = func.FunctionApp()
 @app.function_name(name="HttpTrigger1")
 @app.route(route="hello", auth_level=func.AuthLevel.ANONYMOUS)
 @app.queue_output(arg_name="msg", queue_name="outqueue", connection="AzureWebJobsStorage")
-@app.cosmos_db_output(arg_name="outputDocument", database_name="my-database", collection_name="my-container", connection_string_setting="CosmosDbConnectionString")
+@app.cosmos_db_output(arg_name="outputDocument", database_name="my-database", container_name="my-container", connection="CosmosDbConnectionSetting")
 def test_function(req: func.HttpRequest, msg: func.Out[func.QueueMessage],
     outputDocument: func.Out[func.Document]) -> func.HttpResponse:
      logging.info('Python HTTP trigger function processed a request.')

articles/azure-functions/functions-add-output-binding-cosmos-db-vs-code.md

@@ -24,6 +24,8 @@ items:
        href: use-containers.md
      - name: How to configure the containers
        href: configure-containers.md
+     - name: Reliability in Azure Health Insights
+       href: ../reliability/reliability-health-insights.md?toc=/azure/health-insights/toc.json   
 - name: Responsible use of AI
   expanded: true
   items:

articles/azure-health-insights/TOC.yml

@@ -51,6 +51,10 @@
         href: network-file-system-group-memberships.md
       - name: Understand file locking
         href: understand-file-locks.md  
+      - name: Under volume languages
+        href: understand-volume-languages.md
+      - name: Understand file path lengths 
+        href: understand-path-lengths.md 
   - name: Azure NetApp Files essentials 
     items:
     - name: Storage hierarchy of Azure NetApp Files