removed PII

Author: shellyhaverkamp

articles/healthcare-apis/fhir/deploy-azure-portal.md

@@ -36,7 +36,7 @@ The Azure portal provides a web interface with guided workflows, making it an ef
 
      - **Setting versioning policy (optional)**: The versioning policy controls the history setting for FHIR service at the system level or individual resource type level. For more information, see [FHIR versioning policy and history management](fhir-versioning-policy-and-history-management.md). Choose **Next: Security**.
 
-   - On the **Security settings tab (optional)**, review the fields. 
+   - On the **Security settings** tab, review the fields. 
 
        By default, data is encrypted with Microsoft-managed keys. For additional control over encryption keys, you can supply customer-managed keys to use for encryption of data. Customer-managed keys must be stored in an Azure Key Vault. You can either create your own keys and store them in a key vault, or use the Azure Key Vault APIs to generate keys. For more information, see [Configure customer-managed keys for the FHIR service](configure-customer-managed-keys.md). Choose **Next: Tags**.