Merge pull request #2946 from MicrosoftDocs/portals-1850250

Portals - encryption update - 1850250

Author: tapanm-MSFT

powerapps-docs/maker/portals/admin/add-custom-___domain.md

@@ -6,7 +6,7 @@ manager: kvivek
 ms.service: powerapps
 ms.topic: conceptual
 ms.custom: 
-ms.date: 11/04/2019
+ms.date: 05/29/2020
 ms.author: tapanm
 ms.reviewer:
 ---
@@ -20,16 +20,17 @@ A custom ___domain can help your customers find your support resources more easily
 2. Go to **Portal Actions** > **Add a Custom Domain Name**. A wizard opens to choose the SSL certificate.
 
 3. On the **Choose a SSL certificate** page, select one of the following options:
-   - **Upload a new certificate**: Select this option to upload the .pfx file if you have not yet uploaded it to the organization. Select the upload button underneath **File** to select the .pfx file. After selecting the file, enter the password for your SSL certificate in the **Password** field.
+   - **Upload a new certificate**: Select this option to upload the .pfx file if you haven't yet uploaded it to the organization. Select the upload button underneath **File** to select the .pfx file. After selecting the file, enter the password for your SSL certificate in the **Password** field.
    - **Use an existing certificate**: Select this option to choose the correct certificate from the drop-down list.
 
-     > [!Note]
+     > [!NOTE]
      > The SSL certificate must meet all the following requirements:
-     > - Signed by a trusted certificate authority
-     > - [Exported](https://docs.microsoft.com/powershell/module/pkiclient/export-pfxcertificate?view=win10-ps) as a password-protected PFX file
-     > - Contains private key at least 2048 bits long
-     > - Contains all intermediate certificates in the certificate chain
-     > - Must be SHA2 enabled; SHA1 support is being removed from popular browsers
+     > - Signed by a trusted certificate authority.
+     > - [Exported](https://docs.microsoft.com/powershell/module/pkiclient/export-pfxcertificate?view=win10-ps) as a password-protected PFX file.
+     > - Contains private key at least 2048 bits long.
+     > - Contains all intermediate certificates in the certificate chain.
+     > - Must be SHA2 enabled; SHA1 support is being removed from popular browsers.
+     > - PFX file must be encrypted with TripleDES encryption. Power Apps portals doesn't support AES-256 encryption. 
      > 
      > The steps to export SSL certificate as a password-protected PFX file may vary depending on your certificate provider. Check with your certificate provider for recommendation. For example, certain providers may suggest to use OpenSSL 3rd party tool from [OpenSSL](https://www.openssl.org/) or [OpenSSL Binaries](https://wiki.openssl.org/index.php/Binaries) sites. 
 
@@ -39,15 +40,15 @@ A custom ___domain can help your customers find your support resources more easily
     - **Add a new host name**: Select this option to create a new custom ___domain. Enter the ___domain name you want in the **Domain Name** field.
     - **Use an existing host name**: Select this option to choose a host name from the drop-down list. 
 
-   > [!Note]
+   > [!NOTE]
    > - You can only have one custom ___domain name for a portal. 
    > - To create a custom host name, you will need to create a CNAME with your ___domain provider that points your ___domain to the URL of your portal. If you have just added a CNAME with your ___domain provider, it will take some time to propagate to all DNS servers. If the name is not propagated and you add it here, the following error message will appear: Please add a CNAME record to this ___domain name. Retry after some time passes.
 
-6. Review the information you have entered, and then select **Next** to begin creating the SSL Binding. You should see the message Custom Domain name has been successfully configured for this Portal. You can now go to {Custom Domain Name} to access this portal. {Custom Domain Name} will be a hyperlink to the Custom Portal URL that was just configured.
+6. Review the information you've entered, and then select **Next** to begin creating the SSL Binding. You should see the message Custom Domain name has been successfully configured for this Portal. You can now go to {Custom Domain Name} to access this portal. {Custom Domain Name} will be a hyperlink to the Custom Portal URL that you configured.
 
 7. Select **Finish** to close the wizard.
 
-    > [!Note]
+    > [!NOTE]
     > If you want to change your existing custom ___domain name, you must upload a new SSL certificate and follow the steps as mentioned in this section.