Merge pull request #107380 from priestlg/gdpImmutabilityMast-031120

PRMerger17 · web-flow · commit a692b6fdb16d · 2020-03-12T13:46:50.000-07:00
Added information about immutability policies when adding shares
diff --git a/articles/databox-online/data-box-edge-deploy-add-shares.md b/articles/databox-online/data-box-edge-deploy-add-shares.md
@@ -54,26 +54,28 @@ To create a share, do the following procedure:
     The type can be **SMB** or **NFS**, with SMB being the default. SMB is the standard for Windows clients, and NFS is used for Linux clients.  
     Depending upon whether you choose SMB or NFS shares, the rest of the options vary slightly. 
 
-    c. Provide a storage account where the share will reside. 
+    c. Provide a storage account where the share will reside.
+
+      > [!IMPORTANT]
+      > Make sure that the Azure Storage account that you use does not have immutability policies set on it if you are using it with a Azure Stack Edge or Data Box Gateway device. For more information, see [Set and manage immutability policies for blob storage](https://docs.microsoft.com/azure/storage/blobs/storage-blob-immutability-policies-manage).
 
-    
     d. In the **Storage service** drop-down list, select **Block Blob**, **Page Blob**, or **Files**.  
     The type of service you select depends on which format you want the data to use in Azure. In this example, because we want to store the data as block blobs in Azure, we select **Block Blob**. If you select **Page Blob**, make sure that your data is 512 bytes aligned. For example, a VHDX is always 512 bytes aligned.
 
     e. Create a new blob container or use an existing one from the dropdown list. If creating a blob container, provide a container name. If a container doesn't already exist, it's created in the storage account with the newly created share name.
-   
-    f. Depending on whether you've created an SMB share or an NFS share, do one of the following steps: 
-     
-    - **SMB share**: Under **All privilege local user**, select **Create new** or **Use existing**. If you create a new local user, enter a username and password, and then confirm the password. This action assigns permissions to the local user. Modification of share-level permissions is currently not supported.
+
+    f. Depending on whether you've created an SMB share or an NFS share, do one of the following steps:
+
+    * **SMB share**: Under **All privilege local user**, select **Create new** or **Use existing**. If you create a new local user, enter a username and password, and then confirm the password. This action assigns permissions to the local user. Modification of share-level permissions is currently not supported.
 
         If you select the **Allow only read operations** check box for this share data, you can specify read-only users.
 
         ![Add SMB share](./media/data-box-edge-deploy-add-shares/add-share-smb-1.png)
-   
-    - **NFS share**: Enter the IP addresses of allowed clients that can access the share.
+
+    * **NFS share**: Enter the IP addresses of allowed clients that can access the share.
 
         ![Add NFS share](./media/data-box-edge-deploy-add-shares/add-share-nfs-1.png)
-   
+
 4. Select **Create** to create the share.
     
     You're notified that the share creation is in progress. After the share is created with the specified settings, the **Shares** tile updates to reflect the new share.
diff --git a/articles/databox-online/data-box-edge-manage-shares.md b/articles/databox-online/data-box-edge-manage-shares.md
@@ -48,6 +48,9 @@ Do the following steps in the Azure portal to create a share.
 
 5. From the dropdown list, choose the **Storage service** from block blob, page blob, or files. The type of the service chosen depends on which format you want the data to reside in Azure. For example, in this instance, we want the data to reside as block blobs in Azure, hence we select **Block Blob**. If choosing **Page Blob**, you must ensure that your data is 512 bytes aligned. Use **Page blob** for VHDs or VHDX that are always 512 bytes aligned.
 
+   > [!IMPORTANT]
+   > Make sure that the Azure Storage account that you use does not have immutability policies set on it if you are using it with a Azure Stack Edge or Data Box Gateway device. For more information, see [Set and manage immutability policies for blob storage](https://docs.microsoft.com/azure/storage/blobs/storage-blob-immutability-policies-manage).
+
 6. This step depends on whether you are creating an SMB or an NFS share.
     - **If creating an SMB share** - In the **All privilege local user** field, choose from **Create new** or **Use existing**. If creating a new local user, provide the **username**, **password**, and then confirm password. This assigns the permissions to the local user. After you have assigned the permissions here, you can then use File Explorer to modify these permissions.
 
@@ -166,21 +169,21 @@ The refresh feature allows you to refresh the contents of a share. When you refr
 
 Do the following steps in the Azure portal to refresh a share.
 
-1.	In the Azure portal, go to **Shares**. Select and click the share that you want to refresh.
+1.   In the Azure portal, go to **Shares**. Select and click the share that you want to refresh.
 
     ![Select share](media/data-box-edge-manage-shares/refresh-share-1.png)
 
-2.	Click **Refresh**. 
+2.   Click **Refresh**. 
 
     ![Click refresh](media/data-box-edge-manage-shares/refresh-share-2.png)
  
-3.	When prompted for confirmation, click **Yes**. A job starts to refresh the contents of the on-premises share.
+3.   When prompted for confirmation, click **Yes**. A job starts to refresh the contents of the on-premises share.
 
     ![Confirm refresh](media/data-box-edge-manage-shares/refresh-share-3.png)
  
-4.	While the refresh is in progress, the refresh option is grayed out in the context menu. Click the job notification to view the refresh job status.
+4.   While the refresh is in progress, the refresh option is grayed out in the context menu. Click the job notification to view the refresh job status.
 
-5.	The time to refresh depends on the number of files in the Azure container as well as the files on the device. Once the refresh has successfully completed, the share timestamp is updated. Even if the refresh has partial failures, the operation is considered successful and the timestamp is updated. The refresh error logs are also updated.
+5.   The time to refresh depends on the number of files in the Azure container as well as the files on the device. Once the refresh has successfully completed, the share timestamp is updated. Even if the refresh has partial failures, the operation is considered successful and the timestamp is updated. The refresh error logs are also updated.
 
     ![Updated timestamp](media/data-box-edge-manage-shares/refresh-share-4.png)
  
diff --git a/articles/databox-online/data-box-gateway-deploy-add-shares.md b/articles/databox-online/data-box-gateway-deploy-add-shares.md
@@ -23,10 +23,10 @@ This procedure can take around 10 minutes to complete.
 In this tutorial, you learn how to:
 
 > [!div class="checklist"]
+>
 > * Add a share
 > * Connect to share
 
-
 ## Prerequisites
 
 Before you add shares to your Data Box Gateway, make sure that:
@@ -52,6 +52,8 @@ To create a share do the following procedure:
     2. Select a **Type** for the share. The type can be SMB or NFS, with SMB being the default. SMB is the standard for Windows clients, and NFS is used for Linux clients. Depending upon whether you choose SMB or NFS shares, options presented are slightly different.
 
     3. Provide a storage account where the share will reside. If a container doesn't already exist, it's created in the storage account with the newly created share name. If the container already exists, that container is used.
+       > [!IMPORTANT]
+       > Make sure that the Azure Storage account that you use does not have immutability policies set on it if you are using it with a Azure Stack Edge or Data Box Gateway device. For more information, see [Set and manage immutability policies for blob storage](https://docs.microsoft.com/azure/storage/blobs/storage-blob-immutability-policies-manage).
     
     4. Choose the **Storage service** from block blob, page blob, or files. The type of the service chosen depends on which format you want the data to reside in Azure. For example, in this instance, we want the data to reside as blob blocks in Azure, hence we select Block Blob. If choosing Page Blob, you must ensure that your data is 512 bytes aligned. For example, a VHDX is always 512 bytes aligned.
    
diff --git a/articles/databox-online/data-box-gateway-manage-shares.md b/articles/databox-online/data-box-gateway-manage-shares.md
@@ -40,10 +40,13 @@ Do the following steps in the Azure portal to create a share.
 
 3. Select a **Type** for the share. The type can be **SMB** or **NFS**, with SMB being the default. SMB is the standard for Windows clients, and NFS is used for Linux clients. Depending upon whether you choose SMB or NFS shares, options presented are slightly different.
 
-4. Provide a **Storage account** where the share lives. A container is created in the storage account with the share name if the container already does not exist. If the container already exists, then the existing container is used.
+4. Provide a **Storage account** where the share lives. A container is created in the storage account with the share name if the container already does not exist. If the container already exists, then the existing container is used.  
 
 5. Choose the **Storage service** from block blob, page blob, or files. The type of the service chosen depends on which format you want the data to reside in Azure. For example, in this instance, we want the data to reside as blob blocks in Azure, hence we select **Block Blob**. If choosing**Page Blob**, you must ensure that your data is 512 bytes aligned. For example, a VHDX is always 512 bytes aligned.
 
+   > [!IMPORTANT]
+   > Make sure that the Azure Storage account that you use does not have immutability policies set on it if you are using it with a Azure Stack Edge or Data Box Gateway device. For more information, see [Set and manage immutability policies for blob storage](https://docs.microsoft.com/azure/storage/blobs/storage-blob-immutability-policies-manage).
+
 6. This step depends on whether you are creating an SMB or an NFS share.
     - **If creating an SMB share** - In the **All privilege local user** field, choose from **Create new** or **Use existing**. If creating a new local user, provide the **username**, **password**, and then confirm password. This assigns the permissions to the local user. After you have assigned the permissions here, you can then use File Explorer to modify these permissions.
 
@@ -84,21 +87,21 @@ The refresh feature allows you to refresh the contents of an on-premises share.
 
 Do the following steps in the Azure portal to refresh a share.
 
-1.	In the Azure portal, go to **Shares**. Select and click the share that you want to refresh.
+1.   In the Azure portal, go to **Shares**. Select and click the share that you want to refresh.
 
     ![Select share](media/data-box-gateway-manage-shares/refresh-1.png)
 
-2.	Click **Refresh**. 
+2.   Click **Refresh**. 
 
     ![Click refresh](media/data-box-gateway-manage-shares/refresh-2.png)
  
-3.	When prompted for confirmation, click **Yes**. A job starts to refresh the contents of the on-premises share. 
+3.   When prompted for confirmation, click **Yes**. A job starts to refresh the contents of the on-premises share. 
 
     ![Confirm refresh](media/data-box-gateway-manage-shares/refresh-3.png)
  
-4.	While the refresh is in progress, the refresh option is grayed out in the context menu. Click the job notification to view the refresh job status.
+4.   While the refresh is in progress, the refresh option is grayed out in the context menu. Click the job notification to view the refresh job status.
 
-5.	The time to refresh depends on the number of files in the Azure container as well as the files on the device. Once the refresh has successfully completed, the share timestamp is updated. Even if the refresh has partial failures, the operation is considered successful and the timestamp is updated. 
+5.   The time to refresh depends on the number of files in the Azure container as well as the files on the device. Once the refresh has successfully completed, the share timestamp is updated. Even if the refresh has partial failures, the operation is considered successful and the timestamp is updated. 
 
     ![Updated timestamp](media/data-box-gateway-manage-shares/refresh-4.png)
  
