Merge pull request #295732 from pauljewellmsft/update-classic-account

Update/remove storage articles that reference classic accounts

Author: v-regandowner

articles/storage/.openpublishing.redirection.storage.json

@@ -560,6 +560,11 @@
             "redirect_url": "/azure/storage/blobs/storage-quickstart-blobs-python",
             "redirect_document_id": false
         },
+        {
+            "source_path_from_root": "/articles/storage/blobs/anonymous-read-access-prevent-classic.md",
+            "redirect_url": "/azure/storage/blobs/anonymous-read-access-prevent",
+            "redirect_document_id": false
+        },
         {
             "source_path_from_root": "/articles/storage/blobs/storage-quickstart-blobs-ruby.md",
             "redirect_url": "/previous-versions/azure/storage/blobs/storage-quickstart-blobs-ruby",

articles/storage/blobs/TOC.yml

@@ -386,10 +386,8 @@ items:
         items:
         - name: Overview
           href: anonymous-read-access-overview.md
-        - name: Remediate anonymous access (Azure Resource Manager deployments)
+        - name: Remediate anonymous access
           href: anonymous-read-access-prevent.md
-        - name: Remediate anonymous access (classic deployments)
-          href: anonymous-read-access-prevent-classic.md
         - name: Configure anonymous access
           href: anonymous-read-access-configure.md
     - name: Microsoft Defender for Storage

articles/storage/blobs/anonymous-read-access-configure.md

@@ -6,7 +6,7 @@ author: pauljewellmsft
 ms.author: pauljewell
 ms.service: azure-blob-storage
 ms.topic: how-to
-ms.date: 08/13/2024
+ms.date: 03/04/2025
 ms.reviewer: nachakra
 ms.devlang: powershell
 # ms.devlang: powershell, azurecli
@@ -20,10 +20,7 @@ Azure Storage supports optional anonymous read access for containers and blobs.
 > [!WARNING]
 > When a container is configured for anonymous access, any client can read data in that container. Anonymous access presents a potential security risk, so if your scenario does not require it, we recommend that you remediate anonymous access for the storage account.
 
-This article describes how to configure anonymous read access for a container and its blobs. For information about how to remediate anonymous access for optimal security, see one of these articles:
-
-- [Remediate anonymous read access to blob data (Azure Resource Manager deployments)](anonymous-read-access-prevent.md)
-- [Remediate anonymous read access to blob data (classic deployments)](anonymous-read-access-prevent-classic.md)
+This article describes how to configure anonymous read access for a container and its blobs. For information about how to remediate anonymous access for optimal security, see [Remediate anonymous read access to blob data](anonymous-read-access-prevent.md).
 
 ## About anonymous read access
 

articles/storage/blobs/anonymous-read-access-overview.md

@@ -6,7 +6,7 @@ author: akashdubey-ms
 ms.author: akashdubey
 ms.service: azure-blob-storage
 ms.topic: how-to
-ms.date: 09/12/2023
+ms.date: 03/04/2025
 
 ms.reviewer: nachakra
 ms.custom: devx-track-arm-template
@@ -23,19 +23,9 @@ This article provides an overview of how to remediate anonymous access for your
 
 ## Recommendations for remediating anonymous access
 
-To remediate anonymous access, first determine whether your storage account uses the Azure Resource Manager deployment model or the classic deployment model. For more information, see [Resource Manager and classic deployment](../../azure-resource-manager/management/deployment-models.md).
+You can remediate anonymous access for an account at any time by setting the account's **AllowBlobPublicAccess** property to **False**. After you set the **AllowBlobPublicAccess** property to **False**, all requests for blob data to that storage account will require authorization, regardless of the anonymous access setting for any individual container.
 
-### Azure Resource Manager accounts
-
-If your storage account is using the Azure Resource Manager deployment model, then you can remediate anonymous access for an account at any time by setting the account's **AllowBlobPublicAccess** property to **False**. After you set the **AllowBlobPublicAccess** property to **False**, all requests for blob data to that storage account will require authorization, regardless of the anonymous access setting for any individual container.
-
-If your storage account is using the Azure Resource Manager deployment model, then you can remediate anonymous access for an account at any time by setting the account's **AllowBlobAnonymousAccess** property to **False**. After you set the **AllowBlobAnonymousAccess** property to **False**, all requests for blob data to that storage account will require authorization, regardless of the anonymous access setting for any individual container.
-
-To learn more about how to remediate anonymous access for Azure Resource Manager accounts, see [Remediate anonymous read access to blob data (Azure Resource Manager deployments)](anonymous-read-access-prevent.md).
-
-### Classic accounts
-
-If your storage account is using the classic deployment model, then you can remediate anonymous access by setting each container's access property to **Private**. To learn more about how to remediate anonymous access for classic storage accounts, see [Remediate anonymous read access to blob data (classic deployments)](anonymous-read-access-prevent-classic.md).
+To learn more about how to remediate anonymous access for Azure Resource Manager accounts, see [Remediate anonymous read access to blob data](anonymous-read-access-prevent.md).
 
 ### Scenarios requiring anonymous access
 
@@ -45,5 +35,4 @@ For information on how to configure containers for anonymous access, see [Config
 
 ## Next steps
 
-- [Remediate anonymous read access to blob data (Azure Resource Manager deployments)](anonymous-read-access-prevent.md)
-- [Remediate anonymous read access to blob data (classic deployments)](anonymous-read-access-prevent-classic.md)
+- [Remediate anonymous read access to blob data](anonymous-read-access-prevent.md)