From 14c656a327f3daea485e6e3501b58ed569ad0acf Mon Sep 17 00:00:00 2001
From: Eric Erhardt <eric.erhardt@microsoft.com>
Date: Thu, 3 Oct 2024 16:08:29 -0500
Subject: [PATCH 1/2] Use correct method name in ServiceBus

---
 docs/messaging/azure-service-bus-integration.md | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/docs/messaging/azure-service-bus-integration.md b/docs/messaging/azure-service-bus-integration.md
index d22adba07..2def11590 100644
--- a/docs/messaging/azure-service-bus-integration.md
+++ b/docs/messaging/azure-service-bus-integration.md
@@ -113,14 +113,14 @@ The Service Bus integration supports <xref:Microsoft.Extensions.Configuration?di
 }
 ```
 
-If you have set up your configurations in the `Aspire:Azure:Messaging:ServiceBus` section of your _:::no-loc text="appsettings.json":::_ file you can just call the method `AddAzureServiceBus` without passing any parameters.
+If you have set up your configurations in the `Aspire:Azure:Messaging:ServiceBus` section of your _:::no-loc text="appsettings.json":::_ file you can just call the method `AddAzureServiceBusClient` without passing any parameters.
 
 ### Use inline delegates
 
 You can also pass the `Action<AzureMessagingServiceBusSettings>` delegate to set up some or all the options inline, for example to set the `FullyQualifiedNamespace`:
 
 ```csharp
-builder.AddAzureServiceBus(
+builder.AddAzureServiceBusClient(
     "messaging",
     static settings => settings.FullyQualifiedNamespace = "YOUR_SERVICE_BUS_NAMESPACE");
 ```
@@ -128,7 +128,7 @@ builder.AddAzureServiceBus(
 You can also set up the [ServiceBusClientOptions](/dotnet/api/azure.messaging.servicebus.servicebusclientoptions) using `Action<IAzureClientBuilder<ServiceBusClient, ServiceBusClientOptions>>` delegate, the second parameter of the `AddAzureServiceBus` method. For example to set the `ServiceBusClient` ID to identify the client:
 
 ```csharp
-builder.AddAzureServiceBus(
+builder.AddAzureServiceBusClient(
     "messaging",
     static clientBuilder =>
         clientBuilder.ConfigureOptions(

From 02a02ba421c92a62a48f286d9fa5749d84514fe8 Mon Sep 17 00:00:00 2001
From: Eric Erhardt <eric.erhardt@microsoft.com>
Date: Fri, 4 Oct 2024 09:37:09 -0500
Subject: [PATCH 2/2] Remove named instances section.

---
 .../azure-service-bus-integration.md          | 27 ----------------
 .../azure-security-key-vault-integration.md   | 31 -------------------
 .../azure-storage-tables-integration.md       | 30 ------------------
 3 files changed, 88 deletions(-)

diff --git a/docs/messaging/azure-service-bus-integration.md b/docs/messaging/azure-service-bus-integration.md
index 2def11590..ff45ffbd0 100644
--- a/docs/messaging/azure-service-bus-integration.md
+++ b/docs/messaging/azure-service-bus-integration.md
@@ -135,33 +135,6 @@ builder.AddAzureServiceBusClient(
             static options => options.Identifier = "CLIENT_ID"));
 ```
 
-### Named instances
-
-If you want to add more than one [ServiceBusClient](/dotnet/api/azure.messaging.servicebus.servicebusclient) you can use named instances. Load the named configuration section from the JSON config by calling the `AddAzureServiceBus` method and passing in the `INSTANCE_NAME`.
-
-```csharp
-builder.AddAzureServiceBus("INSTANCE_NAME");
-```
-
-The corresponding configuration JSON is defined as follows:
-
-```json
-{
-  "Aspire": {
-    "Azure": {
-      "Messaging": {
-        "INSTANCE_NAME": {
-          "FullyQualifiedNamespace": "YOUR_SERVICE_BUS_NAMESPACE",
-          "ClientOptions": {
-            "Identifier": "CLIENT_ID"
-          }
-        }
-      }
-    }
-  }
-}
-```
-
 ### Configuration options
 
 The following configurable options are exposed through the <xref:Aspire.Azure.Messaging.ServiceBus.AzureMessagingServiceBusSettings> class:
diff --git a/docs/security/azure-security-key-vault-integration.md b/docs/security/azure-security-key-vault-integration.md
index aa71eb266..f542cdcb0 100644
--- a/docs/security/azure-security-key-vault-integration.md
+++ b/docs/security/azure-security-key-vault-integration.md
@@ -155,37 +155,6 @@ builder.AddAzureKeyVaultSecrets(
             static options => options.DisableChallengeResourceVerification = true))
 ```
 
-### Named instances
-
-If you want to add more than one `SecretClient` you can use named instances. Load the named configuration section from the json config by calling the `AddAzureKeyVaultSecrets` method and passing in the `INSTANCE_NAME`.
-
-```csharp
-builder.AddAzureKeyVaultSecrets("INSTANCE_NAME");
-```
-
-The corresponding configuration JSON is defined as follows:
-
-```json
-{
-  "Aspire": {
-    "Azure": {
-      "Security": {
-        "KeyVault": {
-          "INSTANCE_NAME": {
-            "VaultUri": "YOUR_VAULT_URI",
-            "DisableHealthChecks": false,
-            "DisableTracing": true,
-            "ClientOptions": {
-              "DisableChallengeResourceVerification": true
-            }
-          }
-        }
-      }
-    }
-  }
-}
-```
-
 ### Configuration options
 
 The following configurable options are exposed through the <xref:Aspire.Azure.Security.KeyVault.AzureSecurityKeyVaultSettings> class:
diff --git a/docs/storage/azure-storage-tables-integration.md b/docs/storage/azure-storage-tables-integration.md
index 5fad876a0..cad089375 100644
--- a/docs/storage/azure-storage-tables-integration.md
+++ b/docs/storage/azure-storage-tables-integration.md
@@ -137,36 +137,6 @@ builder.AddAzureTableClient(
             static options => options.EnableTenantDiscovery = true));
 ```
 
-### Named instances
-
-If you want to add more than one <xref:Azure.Data.Tables.TableServiceClient> you can use named instances. Load the named configuration section from the json config by calling the `AddAzureTableClient` method and passing in the `INSTANCE_NAME`.
-
-```csharp
-builder.AddAzureTableClient("INSTANCE_NAME");
-```
-
-The corresponding configuration JSON is defined as follows:
-
-```json
-{
-  "Aspire":{
-    "Azure": {
-      "Data": {
-        "Tables": {
-          "INSTANCE_NAME": {
-            "ServiceUri": "YOUR_URI",
-            "DisableHealthChecks": true,
-            "ClientOptions": {
-              "EnableTenantDiscovery": true
-            }
-          }
-        }
-      }
-    }
-  }
-}
-```
-
 ### Configuration options
 
 The following configurable options are exposed through the <xref:Aspire.Azure.Data.Tables.AzureDataTablesSettings> class: