Merge pull request #267929 from NandiniMurali/patch-3

Enable Update CORS feature

Author: PMEds28

articles/energy-data-services/how-to-enable-cors.md

@@ -20,21 +20,29 @@ You can set CORS rules for each Azure Data Manager for Energy instance. When you
 ## Enabling CORS on Azure Data Manager for Energy instance
 
 1.	Create an **Azure Data Manager for Energy** instance.
-2.	Select the **Resource Sharing(CORS)** tab.
+1.	Select the **Resource Sharing(CORS)** tab.
    [![Screenshot of Resource Sharing(CORS) tab while creating Azure Data Manager for Energy.](media/how-to-enable-cors/enable-cors-1.png)](media/how-to-enable-cors/enable-cors-1.png#lightbox)
 
-3.	In the Resource Sharing(CORS) tab, select **Allowed Origins**. 
-4.	There can be upto 5 **Allowed Origins** added for a given instance.
+1.	In the Resource Sharing(CORS) tab, select **Allowed Origins**. 
+1.	There can be upto 5 **Allowed Origins** added for a given instance.
       [![Screenshot of 1 allowed origin selected.](media/how-to-enable-cors/enable-cors-2.png)](media/how-to-enable-cors/enable-cors-2.png#lightbox)
-5. If you explicitly want to have ***(Wildcard)**, then in the allowed origin * can be added.
-6.	If no setting is enabled on CORS page it's defaulted to Wildcard*, allow all. 
-7. The other values of CORS policy like  **Allowed Methods**, **Allowed Headers**, **Exposed Headers**, **Max age in seconds** are set with default values displayed on the screen.
-7.	Next, select “**Review+Create**” after completing other tabs. 
-8.	Select the "**Create**" button. 
-9.	An **Azure Data Manager for Energy** instance is created with CORS policy.
-10.	Next, once the instance is created the CORS policy set can be viewed in instance **overview** page.
-11. You can navigate to **Resource Sharing(CORS)** and see that CORS is enabled with required **Allowed Origins**.
-    [![Screenshot of viewing the CORS policy set out.](media/how-to-enable-cors/enable-cors-3.png)](media/how-to-enable-cors/enable-cors-3.png#lightbox)
+1. If you explicitly want to have ***(Wildcard)**, then in the allowed origin * can be added.
+1.	If no setting is enabled on CORS page it's defaulted to Wildcard*, allow all. 
+1. The other values of CORS policy like  **Allowed Methods**, **Allowed Headers**, **Exposed Headers**, **Max age in seconds** are set with default values displayed on the screen.
+1.	Next, select “**Review+Create**” after completing other tabs. 
+1.	Select the "**Create**" button. 
+1.	An **Azure Data Manager for Energy** instance is created with CORS policy.
+1.	Next, once the instance is created the CORS policy set can be viewed in instance **overview** page.
+1. You can navigate to **Resource Sharing(CORS)** and see that CORS is enabled with required **Allowed Origins**.
+       [![Screenshot of navigation to CORS update page.](media/how-to-enable-cors/enable-cors-4.png)](media/how-to-enable-cors/enable-cors-4.png#lightbox)
+1. You can modify the Allowed Origins in CORS page at any time after Azure data manager for Energy instance is provisioned.
+   1. For adding a new origin type on the box below.
+       [![Screenshot of adding new origin.](media/how-to-enable-cors/enable-cors-5.png)](media/how-to-enable-cors/enable-cors-5.png#lightbox)
+   1. For deleting an existing allowed origin use the icon.
+      [![Screenshot of deleting the existing origin.](media/how-to-enable-cors/enable-cors-6.png)](media/how-to-enable-cors/enable-cors-6.png#lightbox)
+   1. If * ( wildcard all) is added in any of the allowed origins then please ensure to delete all the other individual allowed origins.
+1. Once the Allowed origin is added, the state of resource provisioning is in “Accepted” and during this time further modifications of CORS policy will not be possible. It takes 15 mins for CORS policies to be updated before update CORS window is available again for modifications.
+     [![Screenshot of CORS update window set out.](media/how-to-enable-cors/enable-cors-7.png)](media/how-to-enable-cors/enable-cors-7.png#lightbox)
 
 ## How are CORS rules evaluated?
 CORS rules are evaluated as follows:
@@ -43,15 +51,10 @@ CORS rules are evaluated as follows:
 
 ## Limitations on CORS policy
 The following limitations apply to CORS rules:
-- You can specify up to five CORS rules per instance.
 - The maximum size of all CORS rules settings on the request, excluding XML tags, shouldn't exceed 2 KiB.
 - The length of allowed origin shouldn't exceed 256 characters.
 
-
 ## Next steps
-- CORS policy once set up during provisioning can be modified only through a Support request
-   > [!div class="nextstepaction"]
-   > [Create an Azure support request](../azure-portal/supportability/how-to-create-azure-support-request.md)
 - To learn more about CORS 
    > [!div class="nextstepaction"]
    > [CORS overview](/rest/api/storageservices/cross-origin-resource-sharing--cors--support-for-the-azure-storage-services)