Merge pull request #218239 from alexwolfmsft/alternate-intro

revamped intro text

Author: v-shils

articles/service-bus-messaging/service-bus-dotnet-get-started-with-queues.md

@@ -18,9 +18,7 @@ In this quickstart, you'll do the following steps:
 4. Write a .NET console application to receive those messages from the queue.
 
 > [!NOTE]
-> - This quick start provides step-by-step instructions to implement a simple scenario of sending a batch of messages to a Service Bus queue and then receiving them. For an overview of the .NET client library, see [Azure Service Bus client library for .NET](https://github.com/Azure/azure-sdk-for-net/blob/main/sdk/servicebus/Azure.Messaging.ServiceBus/README.md). For more samples, see [Service Bus .NET samples on GitHub](https://github.com/Azure/azure-sdk-for-net/tree/master/sdk/servicebus/Azure.Messaging.ServiceBus/samples).
-> - This quick start shows you two ways of connecting to Azure Service Bus: **connection string** and **passwordless**. The first option shows you how to use a connection string to connect to a Service Bus namespace. The second option shows you how to use your security principal in Azure Active Directory and the role-based access control (RBAC) to connect to a Service Bus namespace. You don't need to worry about having hard-coded connection string in your code or in a configuration file or in secure storage like Azure Key Vault. If you are new to Azure, you may find the connection string option easier to follow. We recommend using the passwordless option in real-world applications and production environments. For more information, see [Authentication and authorization](service-bus-authentication-and-authorization.md).
-
+> This quick start provides step-by-step instructions to implement a simple scenario of sending a batch of messages to a Service Bus queue and then receiving them. For an overview of the .NET client library, see [Azure Service Bus client library for .NET](https://github.com/Azure/azure-sdk-for-net/blob/main/sdk/servicebus/Azure.Messaging.ServiceBus/README.md). For more samples, see [Service Bus .NET samples on GitHub](https://github.com/Azure/azure-sdk-for-net/tree/master/sdk/servicebus/Azure.Messaging.ServiceBus/samples).
 
 ## Prerequisites
 

includes/passwordless/service-bus/service-bus-passwordless-template-tabbed.md

@@ -10,21 +10,16 @@ ms.author: alexwolf
 ms.custom: include file
 ---
 
-
-
-## [Passwordless](#tab/passwordless)
-
 ## Authenticate the app to Azure
 
-[!INCLUDE [passwordless-overview](../../../includes/passwordless/passwordless-overview.md)]
+This quick start shows you two ways of connecting to Azure Service Bus: passwordless and connection string. The first option shows you how to use your security principal in Azure Active Directory and role-based access control (RBAC) to connect to a Service Bus namespace. You don't need to worry about having hard-coded connection string in your code or in a configuration file or in a secure storage like Azure Key Vault. The second option shows you how to use a connection string to connect to a Service Bus namespace. If you are new to Azure, you may find the connection string option easier to follow. We recommend using the passwordless option in real-world applications and production environments. For more information, see [Authentication and authorization](../../../articles/service-bus-messaging/service-bus-authentication-and-authorization.md). You can also read more about passwordless authentication on the [overview page](/azure/sdk/authentication?tabs=command-line).
 
-[!INCLUDE [passwordless-default-azure-credential-overview](../../../includes/passwordless/dotnet-default-azure-credential-overview.md)]
+## [Passwordless](#tab/passwordless)
 
 ### Assign roles to your Azure AD user
 
 [!INCLUDE [service-bus-assign-roles](service-bus-assign-roles.md)]
 
-
 ## [Connection String](#tab/connection-string)
 
 ## Get the connection string