Merge pull request MicrosoftDocs#2831 from MicrosoftDocs/portals-issue1204-1809042

Portals issue 1204 fixes - 1809042

Author: KumarVivek

powerapps-docs/maker/portals/add-web-resource.md

@@ -1,30 +1,30 @@
 ---
-title: "Add azure storage web resource to a form | MicrosoftDocs"
-description: "Steps to add azure storage web resource to a form to enable uploading attachments to Azure Storage."
+title: "Add Azure storage web resource to a form | MicrosoftDocs"
+description: "Steps to add Azure storage web resource to a form to enable uploading attachments to Azure Storage."
 author: tapanm-msft
 manager: kvivek
 ms.service: powerapps
 ms.topic: conceptual
 ms.custom: 
-ms.date: 02/11/2020
+ms.date: 05/05/2020
 ms.author: tapanm
 ms.reviewer: tapanm
 ---
 
 # Add the Azure Storage web resource to a form
 
-Attachments uploaded to Azure Storage instead of directly to Common Data Service  can be managed by using notes in Common Data Service .
+Attachments uploaded to Azure Storage instead of directly to Common Data Service can be managed by using notes in Common Data Service.
 
 To enable attachments from a particular form to be uploaded into Azure Storage, you must add a web resource to that form and you must [configure Azure Storage for your organization](enable-azure-storage.md).
 
 > [!NOTE]
-In this example, the form is added to the Lead form for the Lead entity. We recommend using caution when editing existing forms.
+> In this example, the form is added to the Lead form for the Lead entity. We recommend using caution when editing existing forms.
 
-When a file (for example, attachments.zip) is uploaded to Azure Storage by using the portal, it is represented by a note on an entity and a placeholder for the attachment.
+When a file (for example, attachments.zip) is uploaded to Azure Storage by using the portal, it's represented by a note on an entity and a placeholder for the attachment.
 
 ![Attachment on a form](media/notes-attachment-lead-form.png "Placeholder for the attachment on a form")
 
-Note that the attachment file is now named attachment.zip.txt. By default, Common Data Service  has no conception of an Azure file, so this placeholder .txt file is stored in Common Data Service  instead. The Azure Storage context for the placeholder file shows details about the file.
+The attachment file is now named attachment.zip.txt. By default, Common Data Service  has no conception of an Azure file, so this placeholder .txt file is stored in Common Data Service  instead. The Azure Storage context for the placeholder file shows details about the file.
 ```
 {
  Name: attachment.zip,
@@ -34,7 +34,7 @@ Note that the attachment file is now named attachment.zip.txt. By default, Commo
 }
 ```
 
-To see and interact with the file stored in Azure, you must add the web resource adx.annotations.html to the form. As a pre-requisite, ensure that your users have read access to adx_setting. Otherwise, the web resource will not render properly.
+To see and interact with the file stored in Azure, you must add the web resource adx.annotations.html to the form. As a pre-requisite, ensure that your users have read access to adx_setting. Otherwise, the web resource won't render properly.
 
 1. In the form editor for the relevant form, select **Web Resource** on the **Insert** tab.
 
@@ -48,7 +48,7 @@ To see and interact with the file stored in Azure, you must add the web resource
 
 6. Select **OK** to save the resource.
 
-7. Optionally, you might want to remove the existing notes control, or move it to a tab or section that is marked to be not visible by default.
+7. Optionally, you can remove the existing notes control. Or move it to a tab or a section marked to be not visible by default.
 
 8. Save the form, and then publish the changes.
 
@@ -58,25 +58,33 @@ The new control will now be rendered on the page, giving you the ability to mana
 
 ![Azure file attachment on a form](media/azure-file-attachment-lead-form.png "Azure file attachment on a form")
 
-The paper-clip icon has been replaced with a cloud icon to denote that this file is stored in Azure Storage. You can continue to store attachments in Common Data Service ; those files will be denoted with the paper-clip icon.
+The paper-clip icon has been replaced with a cloud icon to denote that this file is stored in Azure Storage. You can continue to store attachments in Common Data Service; those files will be denoted with the paper-clip icon.
 
 > [!Note]
 > You must add cross-origin resource sharing (CORS) rule on your Azure Storage account as follows, otherwise you will see the regular attachment icon rather than the cloud icon.
 > - **Allowed origins**: Specify your ___domain. For example, `https://contoso.crm.dynamics.com`.
 > - **Allowed verbs**: GET, PUT, DELETE, HEAD, POST
 > - **Allowed headers**: Specify the request headers that the origin ___domain may specify on the CORS request. For example, x-ms-meta-data\*, x-ms-meta-target\*. For this scenario, you must specify *, otherwise the web resource will not render properly.
-> - **Exposed headers**: Specify the response headers that may be sent in the response to the CORS request and exposed by the browser to the request issuer. For example, x-ms-meta-\*.
+> - **Exposed headers**: Specify the response headers that may be sent in the response to the CORS request and exposed by the browser to the request issuer. Examples - \* or x-ms-meta-\*. For this scenario, you must specify *, otherwise the web resource will not render properly.
 > - **Maximum age (seconds)**: Specify the maximum amount time that a browser should cache the preflight OPTIONS request. For example, 200.
 > 
 > [!include[More information](../../includes/proc-more-information.md)] [CORS support for the Azure Storage Services](https://docs.microsoft.com/rest/api/storageservices/cross-origin-resource-sharing--cors--support-for-the-azure-storage-services).
 
-If the attached file is an image, the control will display the image as a thumbnail whether it is stored in Common Data Service  or Azure Storage.
+If the attached file is an image, the control will display the image as a thumbnail whether it's stored in Common Data Service  or Azure Storage.
 
 > [!Note]
 > The thumbnail feature is limited to images under 1 MB in size.
 
 ![Notes thumbnail](media/notes-thumbnail.png "Notes thumbnail")
 
+### Processes for Azure Blob Storage
+
+There are two processes that are required to upload attachments to Azure Storage: **Azure Blob Storage Url** and **AzureBlobStorageEnabled**.
+
+![Blob storage processes](media/blob-storage-processes.png "Blob storage processes")
+
+During migration, the processes may get deactivated. This may cause attachments to upload to Common Data Service instead of Azure Storage after you follow steps to add web resource. Ensure these two processes are activated to upload attachments to Azure Storage.
+
 ## CORS protocol support
 
 The [cross-origin resource sharing (CORS)](https://www.w3.org/TR/cors/) protocol consists of a set of headers that indicates whether a response can be shared with another ___domain.
@@ -87,7 +95,7 @@ The following site settings are used to configure CORS:
 | HTTP/Access-Control-Allow-Credentials | Access-Control-Allow-Credentials | The only valid value for this header is true (case-sensitive). If you don't need credentials, omit this header entirely (rather than setting its value to false). 
 | HTTP/Access-Control-Allow-Headers | Access-Control-Allow-Headers | A comma-delimited list of the supported HTTP request headers.
 | HTTP/Access-Control-Allow-Methods | Access-Control-Allow-Methods | A comma-delimited list of the allowed HTTP request methods such as GET, POST, OPTIONS.
-| HTTP/Access-Control-Allow-Origin | Access-Control-Allow-Origin | To allow any resource to access your resources, you can specify \*. Otherwise, specify the URI that can access the resources.                   |
+| HTTP/Access-Control-Allow-Origin | Access-Control-Allow-Origin | URL of the Dynamics 365 instance, such as https://contoso.crm.dynamics.com. To allow any URI to access your resources, use \*.                 |
 |  HTTP/Access-Control-Expose-Headers | Access-Control-Expose-Headers | A comma-delimited list of HTTP header names other than the simple response headers that the resource might use and can be exposed.
 | HTTP/Access-Control-Max-Age | Access-Control-Max-Age |  Maximum number of seconds the results can be cached.
 | HTTP/Content-Security-Policy | Content-Security-Policy | Controls resources the user agent is allowed to load for a given page.