Daily Defender News
Aboutmerill.net
Microsoft Defender for Cloud
Cloud and workloads

Migrate from Defender for Storage (classic)

4 September 2026Doc update+14 / −8 lines

In brief

The page now explicitly states that moving to the new Defender for Storage plan cannot be reversed, expands the benefits description, clarifies policy behavior, and updates migration-method guidance and script references.

What Defender admins need to know

Review the updated guidance before migrating, because switching prevents returning to the classic plans.

Summaries are generated from the documentation change itself.

Documentation change

View full page diffView on Microsoft Learn

The comparison below shows only the changed extract. Use the full-page view for complete context.

Migrate from Defender for Storage (classic)

The new pricing plan charges based on the number of storage accounts you protect, simplifying calculations and allowing for easy scaling as your needs change. For detailed pricing information, see the pricing page. You can also estimate costs with the Defender for Cloud cost calculator.

To take advantage of these features,the enhanced monitoring, malware scanning, sensitive data detection, and predictable pricing in the new plan, we recommend moving to the new Defender for Storage plan by February 5, 2025.

Impact on the Defender for Storage (classic) per-transaction plan

The classic per-transaction plan will no longer be available for new storage accounts and subscriptions. Existing accounts will retain the plan without future features and updates, so we encourage you to move to the new plan for the enhanced features and simplified pricing. If your subscription or storage account already has the classic per-transaction plan enabled, it will remain active, but enabling this plan at the resource level will only be possible for these existing subscriptions.

If you have policies that enforce the classic per-transaction plan without specifying the per-transaction subplan, existing subscriptions will retain the classic per-transaction plan already enabled on those subscriptions, while new subscriptions will default to the new plan. However, if you specify the per-transaction subplan, the policy assignment will fail for new subscriptions. Once you switch to the new plan, you can no longer revert to the Defender for Storage (classic) per-transaction or per-storage account plans at either the subscription or storage account level.

Identify active Defender for Storage plans

| project properties, tenantId, subscriptionId, IsInTrialPeriod, IsEnabled, DefenderForStoragePlan, MalwareScanningEnabled, MalwareScanningCapping, SensitiveDataDiscoveryEnabled
```

Migration methodsChoose a migration method for Defender for Storage (classic)

To enable and configure the new Microsoft Defender for Storage plan, you have several options:

Azure Resource Graph Explorer

To identify active policies in your subscription using Azure Resource Graph Explorer, run the following query. This query searches Azure Resource Graph for policy assignments scoped to the specified subscription that includesmatch the old Defender for Storage policies.policy names. If you have custom policies, modify the query accordingly: 

policyresources

### PowerShell

To identify active policies in your subscription using PowerShell, run:run the following command. This command lists all Azure Policy assignments at the subscription scope so you can verify which Defender for Storage policies are applied:

```powershell
Get-AzPolicyAssignment -Scope "/subscriptions/{subscriptionId}"

Next stepsteps

In this article, you learned about migrating to the new Microsoft Defender for Storage plan.