Update all feature for redis kafka (#824)

docs/src/main/asciidoc/authentication.adoc

@@ -10,6 +10,7 @@
 :azure-storage-blob-data-owner: https://docs.microsoft.com/azure/role-based-access-control/built-in-roles#storage-blob-data-owner
 :azure-storage-blob-data-reader: https://docs.microsoft.com/azure/role-based-access-control/built-in-roles#storage-blob-data-reader
 :azure-storage-queue-data-reader: https://docs.microsoft.com/azure/role-based-access-control/built-in-roles#storage-queue-data-reader
+:azure-redis-cache-contributor: https://docs.microsoft.com/azure/role-based-access-control/built-in-roles#redis-cache-contributor
 :key-vault-access-policy: https://docs.microsoft.com/azure/key-vault/general/assign-access-policy
 :cosmos-db-rbac: https://docs.microsoft.com/azure/cosmos-db/how-to-setup-rbac
 :managed-identity: https://docs.microsoft.com/azure/active-directory/managed-identities-azure-resources/overview
@@ -18,9 +19,9 @@
 
 === DefaultAzureCredential
 
-The `DefaultAzureCredential` is appropriate for most scenarios where the application is intended to ultimately be run in the Azure Cloud.This is because the DefaultAzureCredential combines credentials commonly used to authenticate when deployed, with credentials used to authenticate in a development environment.
+The `DefaultAzureCredential` is appropriate for most scenarios where the application is intended to ultimately be run in the Azure Cloud. This is because the DefaultAzureCredential combines credentials commonly used to authenticate when deployed, with credentials used to authenticate in a development environment.
 
-NOTE: DefaultAzureCredential is intended to simplify getting started with the SDK by handling common scenarios with reasonable default behaviors.Developers who want more control or whose scenario isn't served by the default settings should use other credential types.
+NOTE: DefaultAzureCredential is intended to simplify getting started with the SDK by handling common scenarios with reasonable default behaviors. Developers who want more control or whose scenario isn't served by the default settings should use other credential types.
 
 The `DefaultAzureCredential` will attempt to authenticate via the following mechanisms in order.
 
@@ -144,8 +145,13 @@ Following are the Azure built-in roles for authorizing access to Azure services
 |link:{azure-storage-queue-data-reader}[Storage Queue Data Reader]
 |Read and list Azure Storage queues and queue messages.
 
+|link:{azure-redis-cache-contributor}[Redis Cache Contributor]
+|Manage Redis caches.
+
 |===
 
+NOTE: When using Spring Cloud Azure Resource Manager to get the connection strings of Event Hubs, Service Bus, and Storage Queue, or properties of Cache for Redis, assign the Azure built-in role `Contributor`. Azure Cache for Redis is special, and you can also assign the `Redis Cache Contributor` role to get the Redis properties.
+
 NOTE: A Key Vault access policy determines whether a given security principal, namely a user, application or user group, can perform different operations on Key Vault secrets, keys, and certificates. You can assign access policies using the Azure portal, the Azure CLI, or Azure PowerShell. Check {key-vault-access-policy}[here] for more details.
 
 IMPORTANT: Azure Cosmos DB exposes 2 built-in role definitions: `Cosmos DB Built-in Data Reader` and `Cosmos DB Built-in Data Contributor`. However, Azure portal support for role management is not available yet. Check {cosmos-db-rbac}[here] for more details about the permission model, role definitions, and role assignment.

docs/src/main/asciidoc/kafka-support.adoc

@@ -1,7 +1,7 @@
 [#kafka-support]
 == Kafka Support
 
-Connect to Azure Event Hubs using Spring Kafka libraries. There are two approaches to connect to Azure Event Hubs for Kafka, the first one is to provide the Azure Event Hubs connection string directly, the other is to use Azure Resource Manager to retrieve the connection string.
+Connect to Azure Event Hubs (link:https://azure.microsoft.com/pricing/details/event-hubs/#explore-pricing-options[Basic pricing tier is not supported]) using Spring Kafka libraries. There are two approaches to connect to Azure Event Hubs for Kafka, the first one is to provide the Azure Event Hubs connection string directly, the other is to use Azure Resource Manager to retrieve the connection string.
 
 === Dependency Setup
 
@@ -25,7 +25,6 @@ If you want to retrieve the connection string using Azure Resource Manager, plea
 </dependency>
 ----
 
-
 === Configuration
 
 NOTE: If you choose to use a security principal to authenticate and authorize with Azure Active Directory for accessing an Azure resource, please refer to link:index.html#authorize-access-with-azure-active-directory[Authorize access with Azure AD] to make sure the security principal has been granted the sufficient permission to access the Azure resource.

docs/src/main/asciidoc/redis-support.adoc

@@ -1,7 +1,7 @@
 [#redis-support]
 == Redis Support
 
-Connect to Azure Cache for Redis using Spring Redis libraries.With adding `spring-cloud-azure-starter` and `spring-cloud-azure-resourcemanager` to your application, it's possible to read the Azure Cache for Redis connection information through Azure Resource Manager and auto-configure the Redis properties.
+Connect to Azure Cache for Redis using Spring Redis libraries. With adding `spring-cloud-azure-starter` and `spring-cloud-azure-resourcemanager` to your application, it's possible to read the Azure Cache for Redis connection information through Azure Resource Manager and auto-configure the Redis properties.
 
 === Dependency Setup