Merge branch 'main' of https://github.com/MicrosoftDocs/azure-docs-pr into afd-faq

Author: halkazwini

articles/azure-functions/functions-bindings-mcp.md

@@ -86,6 +86,9 @@ You can use the `extensions.mcp` section in `host.json` to define MCP server inf
       "encryptClientState": true,
       "messageOptions": {
         "useAbsoluteUriForEndpoint": false
+      },
+      "system": {
+        "webhookAuthorizationLevel": "System"
       }
     }    
   }
@@ -100,6 +103,8 @@ You can use the `extensions.mcp` section in `host.json` to define MCP server inf
 | **encryptClientState** | Determines if client state is encrypted. Defaults to true. Setting to false may be useful for debugging and test scenarios but isn't recommended for production. |
 | **messageOptions** | Options object for the message endpoint in the SSE transport. |
 | **messageOptions.UseAbsoluteUriForEndpoint** | Defaults to `false`. Only applicable to the server-sent events (SSE) transport; this setting doesn't affect the Streamable HTTP transport. If set to `false`, the message endpoint is provided as a relative URI during initial connections over the SSE transport. If set to `true`, the message endpoint is returned as an absolute URI. Using a relative URI isn't recommended unless you have a specific reason to do so.|
+| **system** | Options object for system-level configuration. |
+| **system.webhookAuthorizationLevel** | Defines the authorization level required for the webhook endpoint. Defaults to "System". Allowed values are "System" and "Anonymous". When you set the value to "Anonymous", an access key is no longer required for requests. Regardless of if a key is required or not, you can use [built-in MCP server authorization][authorization] as an identity-based access control layer.<br/>This setting is only available when running on Functions host version 4.1045.0 or later.|
 
 ## Connect to your MCP server
 
@@ -112,7 +117,9 @@ To connect to the MCP server exposed by your function app, you need to provide a
 
 <sup>1</sup> Newer protocol versions deprecated the Server-Sent Events transport. Unless your client specifically requires it, you should use the Streamable HTTP transport instead.
 
-When hosted in Azure, the endpoints exposed by the extension also require the [system key](./function-keys-how-to.md) named `mcp_extension`. If it isn't provided in the `x-functions-key` HTTP header or in the `code` query string parameter, your client receives a `401 Unauthorized` response. You can retrieve the key using any of the methods described in [Get your function access keys](./function-keys-how-to.md#get-your-function-access-keys). The following example shows how to get the key with the Azure CLI:
+When hosted in Azure, by default, the endpoints exposed by the extension also require the [system key](./function-keys-how-to.md) named `mcp_extension`. If it isn't provided in the `x-functions-key` HTTP header or in the `code` query string parameter, your client receives a `401 Unauthorized` response. You can remove this requirement by setting the `system.webhookAuthorizationLevel` property in `host.json` to `Anonymous`. For more information, see the [host.json settings](#hostjson-settings) section.
+
+You can retrieve the key using any of the methods described in [Get your function access keys](./function-keys-how-to.md#get-your-function-access-keys). The following example shows how to get the key with the Azure CLI:
 
 ```azurecli
 az functionapp keys list --resource-group <RESOURCE_GROUP> --name <APP_NAME> --query systemKeys.mcp_extension --output tsv

articles/partner-solutions/apache-kafka-confluent-cloud/add-confluent-connectors.md

@@ -1,22 +1,19 @@
 ---
-title: Use Confluent Connectors in Azure (Preview)
+title: Create a Confluent Connector for Azure Blob Storage (Preview)
 description: Learn how to use Confluent Connectors in Azure (preview) to connect an instance of Apache Kafka & Apache Flink on Confluent Cloud to Azure Blob Storage.
 ms.topic: how-to
-ms.date: 05/28/2024
+ms.date: 10/30/2025
 ms.author: malev
 author: maud-lv
 
-#customer intent: As a developer, I want learn how to connect an instance of Apache Kafka & Apache Flink on Confluent Cloud to Azure Blob Storage so that I can use Confluent Connectors in Azure.
+#customer intent: As a developer, I want to learn how to connect an instance of Apache Kafka & Apache Flink on Confluent Cloud to Azure Blob Storage so that I can use Confluent Connectors in Azure.
 ---
 
-# Use Confluent Connectors in Azure (preview)
+# Create a Confluent Connector to Azure Blob Storage (preview)
 
-Confluent Cloud helps you connect your Confluent clusters to popular data sources and sinks. The solution is available on Azure by using the Confluent Connectors feature.
+Confluent Cloud helps you connect your Confluent clusters to popular data sources and sinks. You can take advantage of this solution on Azure by using the Confluent Connectors feature.
 
-> [!NOTE]
-> Currently, Apache Kafka & Apache Flink on Confluent Cloud, an Azure Native Integrations service, supports only Confluent Connectors for Azure Blob Storage. It supports both source and sink connectors in Azure Blob Storage.
-
-In this article, learn how to connect an instance of Apache Kafka & Apache Flink on Confluent Cloud to Azure Blob Storage.
+In this article, you'll learn how to connect an instance of Apache Kafka & Apache Flink on Confluent Cloud to Azure Blob Storage.
 
 ## Prerequisites
 
@@ -36,7 +33,7 @@ To create a sink connector for Azure Blob Storage:
    :::image type="content" source="./media/confluent-connectors/create-new-connector.png" alt-text="Screenshot that shows the Confluent Connectors menu in the Azure portal.":::
 
 1. Select **Create new connector**.
-1. On the **Create a new connector** pane, configure the settings that are described in the next sections.
+1. In the **Create a new connector** pane, configure the settings that are described in the next sections.
 
 ### Basics
 
@@ -56,13 +53,14 @@ On the **Basics** tab, enter or select values for the following settings:
 
 :::image type="content" source="./media/confluent-connectors/basic-sink.png" alt-text="Screenshot that shows the Basics tab and creating a sink connector in the Azure portal.":::
 
-Then, select **Next**.
+Select **Next**.
 
 ### Authentication
 
-On the **Authentication** tab, you can configure the authentication of your Kafka cluster via API keys. By default, **Create New** is selected and API keys are automatically generated and configured when the connector is created.
+On the **Authentication** tab, select an authentication method: **User** or **Service account**. 
 
-Leave the default values and select the **Configuration** tab.
+- To use a service account (recommended for production), enter a **Service account** name and continue. A new service account will be provisioned in Confluent cloud when the connector is created. 
+- To use a user account, leave **User** selected and continue. A user API key and secret will be created for the specific user in Confluent cloud when the connector is created. 
 
 :::image type="content" source="./media/confluent-connectors/authentication.png" alt-text="Screenshot that shows the Authentication tab in the Azure portal.":::
 
@@ -72,30 +70,30 @@ On the **Configuration** tab, enter or select the following values, and then sel
 
 | Setting | Action |
 | --- | --- |
-| **Input Data Format**  | Select an input Kafka record data format type: AVRO, JSON, string, or Protobuf. |
-| **Output Data Format** | Select an output data format: AVRO, JSON, string, or Protobuf. |
+| **Input Data Format**  | Select an input Kafka record data format type: **AVRO**, **JSON**, **string**, or **Protobuf**. |
+| **Output Data Format** | Select an output data format: **AVRO**, **JSON**, **string**, or **Protobuf**. |
 | **Time Interval**      | Select the time interval in which to group the data. Choose between hourly and daily. |
 | **Flush size**         | Optionally, you can enter a flush size. The default flush size is 1,000. |
-| **Number of tasks**    | Optionally, you can enter the maximum number of simultaneous tasks you want your connector to support. The default is 1. |
+| **Number of tasks**    | Optionally, you can enter the maximum number of simultaneous tasks you want your connector to support. The default is **1**. |
 
 :::image type="content" source="./media/confluent-connectors/configuration-sink.png" alt-text="Screenshot that shows the Configuration tab for a sink connector in the Azure portal.":::
 
 Select **Review + create** to continue.
 
 ### Review + create
 
-Review your settings for the connector to ensure that the details are accurate and complete. Then, select **Create** to begin the connector deployment.
+Review your settings for the connector to ensure that the details are accurate and complete. Then select **Create** to begin the connector deployment.
 
-In the upper-right corner of the Azure portal, a notification displays the deployment status. When it shows the status *Completed*, refresh the **Confluent Connectors (Preview)** pane and check for the new connector tile on this pane.  
+In the upper-right corner of the Azure portal, a notification displays the deployment status. When the status is **Completed**, refresh the **Confluent Connectors (Preview)** pane and check for the new connector tile on this pane.  
 
 ## Create a Confluent source Connector for Azure Blob Storage (preview)
 
 1. In the Azure portal, go to your Confluent organization.
-1. On the left menu, select **Confluent** > **Confluent Connectors (Preview)**.
+1. In the left pane, select **Confluent** > **Confluent Connectors (Preview)**.
 
    :::image type="content" source="./media/confluent-connectors/create-new-connector.png" alt-text="Screenshot that shows the Confluent Connectors menu in the Azure portal.":::
 
-1. On the **Create a new connector** pane, select **Create new connector**.
+1. In the **Create a new connector** pane, select **Create new connector**.
 
 ### Basics
 
@@ -114,13 +112,14 @@ On the **Basics** tab, enter or select values for the following settings:
 
 :::image type="content" source="./media/confluent-connectors/basic-source.png" alt-text="Screenshot that shows the Basics tab and creating a source connector in the Azure portal.":::
 
-Then, select **Next**.
+Select **Next**.
 
 ### Authentication
 
-On the **Authentication** tab, you can configure the authentication of your Kafka cluster via API keys. By default, **Create New** is selected and API keys are automatically generated and configured when the connector is created.
+On the **Authentication** tab, select an authentication method: **User** or **Service account**. 
 
-Leave the default values and select the **Configuration** tab.
+- To use a service account (recommended for production), enter a **Service account** name and continue. A new service account will be provisioned in Confluent cloud when the connector is created. 
+- To use a user account, leave **User** selected and continue. A user API key and secret will be created for the specific user in Confluent cloud when the connector is created. 
 
 :::image type="content" source="./media/confluent-connectors/authentication.png" alt-text="Screenshot that shows the Authentication tab in the Azure portal.":::
 
@@ -130,38 +129,21 @@ On the **Configuration** tab, enter or select values for the following settings:
 
 | Name | Action |
 | --- | --- |
-| **Input Data Format**  | Select an input Kafka record data format type: AVRO, JSON, string, Protobuf. |
-| **Output Data Format** | Select an output data format: AVRO, JSON, string, or Protobuf. |
+| **Input Data Format**  | Select an input Kafka record data format type: **AVRO**, **JSON**, **string**, **Protobuf**. |
+| **Output Data Format** | Select an output data format: **AVRO**, **JSON**, **string**, or **Protobuf**. |
 | **Topic name and regex** | Configure the topic name and the regex pattern of your messages to ensure they're mapped. For example, `*my-topic:.*\.json+` moves all the files that have the `.json` extension into `my-topic`. |
 | **Flush size**         | (Optional) Enter a flush size. The default flush size is 1,000. |
-| **Number of tasks**    | (Optional) Enter the maximum number of simultaneous tasks you want your connector to support. The default is 1. |
+| **Number of tasks**    | (Optional) Enter the maximum number of simultaneous tasks you want your connector to support. The default is **1**. |
 
 :::image type="content" source="./media/confluent-connectors/configuration-source.png" alt-text="Screenshot that shows the Configuration tab and creating a source connector in the Azure portal.":::
 
 Select **Review + create** to continue.
 
 ### Review + create
 
-Review your settings for the connector to ensure that the details are accurate and complete. Then, select **Create** to begin the connector deployment.
-
-In the upper-right corner of the Azure portal, a notification displays the deployment status. When it shows the status *Completed*, refresh the **Confluent Connectors (Preview)** pane and check for the new connector tile on this pane.  
-
-## Manage Azure Confluent Connectors (preview)
-
-1. In the Azure portal, go to your Confluent organization.
-1. On the left menu, select **Confluent** > **Confluent Connectors**.
-1. Select your environment and cluster.
-
-The Azure portal shows a list of Azure connectors for the environment and cluster.
-
-You can also complete the following optional actions:
-
-* Filter connectors by **Type** (**Source** or **Sink**) and **Status** (**Running**, **Failed**, **Provisioning**, or **Paused**).
-* Search for a connector by name.
-
-   :::image type="content" source="./media/confluent-connectors/display-connectors.png" alt-text="Screenshot that shows a list of existing connectors on the Confluent Connectors tab in the Azure portal." lightbox="./media/confluent-connectors/display-connectors.png":::
+Review your settings for the connector to ensure that the details are accurate and complete. Then select **Create** to begin the connector deployment.
 
-   To learn more about a connector, select the connector tile to open Confluent. In the Confluent UI, you can see the connector health, throughput, and other information. You also can edit and delete the connector.
+In the upper-right corner of the Azure portal, a notification displays the deployment status. When the status is **Completed**, refresh the **Confluent Connectors (Preview)** pane and check for the new connector tile on this pane.
 
 ## Related content