Update Azure Cache for Redis docs (#612)

Remove the disabling of TLS and add a sample for adding Redis Cache with TLS enabled. Also, fix some Markdown issues. Fixes #580

howto/configure-redis/README.md

@@ -9,7 +9,7 @@ Dapr can use Redis in two ways:
 
 Dapr can use any Redis instance - containerized, running on your local dev machine, or a managed cloud service. If you already have a Redis store, move on to the [Configuration](#configuration) section.
 
-### Creating a Redis Cache in your Kubernetes Cluster using Helm
+### Option 1: Creating a Redis Cache in your Kubernetes Cluster using Helm
 
 We can use [Helm](https://helm.sh/) to quickly create a Redis instance in our Kubernetes cluster. This approach requires [Installing Helm v3](https://github.com/helm/helm#install).
 
@@ -46,20 +46,28 @@ helm install redis bitnami/redis
      value: lhDOkwTlp0
    ```
 
-### Creating an Azure Managed Redis Cache
+### Option 2: Creating an managed Azure Cache for Redis service
 
-**Note**: this approach requires having an Azure Subscription.
+> **Note**: This approach requires having an Azure Subscription.
 
-1. Open [this link](https://ms.portal.azure.com/#create/Microsoft.Cache) to start the Azure Redis Cache creation flow. Log in if necessary.
-2. Fill out necessary information and **check the "Unblock port 6379" box**, which will allow us to persist state without SSL.
-3. Click "Create" to kickoff deployment of your Redis instance.
-4. Once your instance is created, you'll need to grab your access key. Navigate to "Access Keys" under "Settings" and copy your key.
-5. Run `kubectl get svc` and copy the cluster IP of your `redis-master`.
-6. Finally, we need to add our key and our host to a `redis.yaml` file that Dapr can apply to our cluster. If you're running a sample, you'll add the host and key to the provided `redis.yaml`. If you're creating a project from the ground up, you'll create a `redis.yaml` file as specified in [Configuration](#configuration). Set the `redisHost` key to `[IP FROM PREVIOUS STEP]:6379` and the `redisPassword` key to the key you copied in step 4. **Note:** In a production-grade application, follow [secret management](../../concepts/secrets/README.md) instructions to securely manage your secrets.
+1. Open the [Azure Portal](https://ms.portal.azure.com/#create/Microsoft.Cache) to start the Azure Redis Cache creation flow. Log in if necessary.
+1. Fill out the necessary information
+1. Click "Create" to kickoff deployment of your Redis instance.
+1. Once your instance is created, you'll need to grab your access key. Navigate to "Access Keys" under "Settings" and copy your key.
+1. We  need the hostname of your Redis instance, which we can retrieve from the "Overview" in Azure. It should look like `xxxxxx.redis.cache.windows.net:6380`.
+1. Finally, we need to add our key and our host to a `redis.yaml` file that Dapr can apply to our cluster. If you're running a sample, you'll add the host and key to the provided `redis.yaml`. If you're creating a project from the ground up, you'll create a `redis.yaml` file as specified in [Configuration](#configuration).
+
+   As the connection to Azure is encrypted, make sure to add the following block to the `metadata` section of your `redis.yaml` file.
+
+   ```yaml
+   metadata:
+   - name: enableTLS
+     value: "true"
+   ```
 
 > **NOTE:** Dapr pub/sub uses [Redis Streams](https://redis.io/topics/streams-intro) that was introduced by Redis 5.0, which isn't currently available on Azure Managed Redis Cache. Consequently, you can use Azure Managed Redis Cache only for state persistence.
 
-### Other ways to Create a Redis Database
+### Other options to create a Redis Database
 
 - [AWS Redis](https://aws.amazon.com/redis/)
 - [GCP Cloud MemoryStore](https://cloud.google.com/memorystore/)