Merge pull request #247635 from kasun04/main

Fix MSI capture ARM template issue.

Author: v-regandowner

articles/event-hubs/TOC.yml

@@ -70,7 +70,7 @@
           href: create-schema-registry.md
         - name: Validate schemas for Kafka applications 
           href: schema-registry-kafka-java-send-receive-quickstart.md
-        - name: Validate schemas with Avro for Event Hubs SDK 
+        - name: Validate schemas for Event Hubs SDK based applications 
           href: schema-registry-dotnet-send-receive-quickstart.md
     - name: Create a dedicated cluster
       href: event-hubs-dedicated-cluster-create-portal.md

articles/event-hubs/event-hubs-capture-managed-identity.md

@@ -52,7 +52,7 @@ The Event Hubs Capture feature also support capturing data to a capture destinat
 
 For that you can use the same ARM templates given in [enabling capture with ARM template guide](./event-hubs-resource-manager-namespace-event-hub-enable-capture.md) with corresponding managed identity. 
 
-For example, following ARM template can be used to create an event hub with capture enabled. Azure Storage or Azure Data Lake Storage Gen 2 can be used as the capture destination and system assigned identity is used as the authentication method. The resource ID of the destination can point to a resource in a different subscription. 
+For example, following ARM template can be used to create an event hub with capture enabled. Azure Storage or Azure Data Lake Storage Gen 2 can be used as the capture destination and user assigned identity is used as the authentication method. The resource ID of the destination can point to a resource in a different subscription. 
 
 ```json
 "resources":[
@@ -86,9 +86,6 @@ For example, following ARM template can be used to create an event hub with capt
           "dependsOn": [
             "[concat('Microsoft.EventHub/namespaces/', parameters('eventHubNamespaceName'))]"
           ],
-          "identity": {
-            "type": "SystemAssigned",
-          },
           "properties": {
             "messageRetentionInDays": "[parameters('messageRetentionInDays')]",
             "partitionCount": "[parameters('partitionCount')]",
@@ -104,7 +101,13 @@ For example, following ARM template can be used to create an event hub with capt
                   "storageAccountResourceId": "[parameters('destinationStorageAccountResourceId')]",
                   "blobContainer": "[parameters('blobContainerName')]",
                   "archiveNameFormat": "[parameters('captureNameFormat')]"
-                }
+                },
+               "identity": {
+                 "type": "UserAssigned",
+                 "userAssignedIdentities": {
+                   "xxxxxxxx": {}
+                  }
+          						}
               }
             }
           }