SOLVED

Possible to Disable Defender on individual Storage Accounts?

%3CLINGO-SUB%20id%3D%22lingo-sub-2737804%22%20slang%3D%22en-US%22%3EPossible%20to%20Disable%20Defender%20on%20individual%20Storage%20Accounts%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2737804%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20folks%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CDIV%3EThe%20gist%20is%20that%20we%20have%20Azure%20Defender%20enabled%20at%20a%20Subscription%20level.%26nbsp%3B%20With%20that%20comes%20Advanced%20Threat%20Protection%20for%20Storage%20Accounts%20which%20is%20charged%26nbsp%3Bper%20transaction%20within%20those%20Storage%20Accounts.%3C%2FDIV%3E%3CDIV%3E%26nbsp%3B%3C%2FDIV%3E%3CDIV%3EWe%20have%20four%20storage%20accounts%20out%20of%20176%20that%20are%20very%20highly%20transactional%20and%20the%20monthly%20billing%20for%20Advanced%20Threat%20Protection%20is%20close%20to%20%241%2C000.%26nbsp%3B%20They%20are%20internal%20storage%20accounts%20with%20very%20limited%20public%20exposure%20so%20we%20are%20not%20worried%20about%20threats%26nbsp%3Bwithin%20those%20transactions.%26nbsp%3B%26nbsp%3B%3C%2FDIV%3E%3CDIV%3E%26nbsp%3B%3C%2FDIV%3E%3CDIV%3EOur%20ideal%20scenario%20would%20be%20to%20keep%20Defender%20enabled%20at%20the%20subscription%20level%20for%20all%20of%20our%20Storage%20accounts%20and%20all%20future%20storage%20accounts%20but%20not%20be%20billed%20for%20(or%20use)%20Advanced%20Threat%20Protection.%26nbsp%3B%20It%20seems%20like%20this%20cmdlet%3A%3C%2FDIV%3E%3CDIV%3E%26nbsp%3B%3C%2FDIV%3E%3CDIV%3E%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fpowershell%2Fmodule%2Faz.security%2Fdisable-azsecurityadvancedthreatprotection%3Fview%3Dazps-6.3.0%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fpowershell%2Fmodule%2Faz.security%2Fdisable-azsecurityadvancedthreatprotection%3Fview%3Dazps-6.3.0%3C%2FA%3E%3C%2FDIV%3E%3CDIV%3E%26nbsp%3B%3C%2FDIV%3E%3CDIV%3EShould%20do%20the%20job%2C%20but%20it%20does%20not.%26nbsp%3B%20Either%20it%20does%20not%20disable%20ATP%20or%20it%20does%20not%20disable%20the%20billing.%26nbsp%3B%20In%20either%20of%20those%20cases%20it%20does%20not%20do%20what%20we%20need.%3C%2FDIV%3E%3CDIV%3E%26nbsp%3B%3C%2FDIV%3E%3CDIV%3EAfter%202.5%20months%20or%20trying%20to%20work%20through%20it%20the%20only%20option%20I%20have%20been%20given%20is%20to%20disable%20Defender%20at%20the%20Subscription%20level%20for%20all%20of%20our%20Storage%20Accounts%2C%20and%20then%20re-enable%20the%20172%20storage%20accounts%20that%20we%20do%20want%20Defender%20for%20individually%20via%20PS.%26nbsp%3B%20That%20will%20and%20does%20work%2C%20but%20it%20will%20require%20overhead%20on%20our%20part%20to%20ensure%20they%20all%20stay%20enabled%20and%20that%20any%20future%20accounts%20are%20enabled%20by%20the%20creator%20and%20none%20get%20missed.%26nbsp%3B%26nbsp%3B%3C%2FDIV%3E%3CDIV%3E%26nbsp%3B%3C%2FDIV%3E%3CDIV%3EDo%20we%20have%20any%20other%20avenues%20to%20suppress%20Advanced%20Threat%20Protection%20on%20a%20subset%20of%20accounts%20within%20a%20Subscription%3F%26nbsp%3B%26nbsp%3B%3C%2FDIV%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2754187%22%20slang%3D%22en-US%22%3ERe%3A%20Possible%20to%20Disable%20Defender%20on%20individual%20Storage%20Accounts%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2754187%22%20slang%3D%22en-US%22%3EThis%20option%20to%20selectively%20disable%20Defender%20for%20certain%20storage%20accounts%20is%20currently%20being%20tested%20(closed%20private%20preview)%20and%20will%20likely%20be%20released%20later%20this%20year.%20No%20solid%20ETA%20though.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2754332%22%20slang%3D%22en-US%22%3ERe%3A%20Possible%20to%20Disable%20Defender%20on%20individual%20Storage%20Accounts%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2754332%22%20slang%3D%22en-US%22%3EThank%20you%20Stanislav%2C%3CBR%20%2F%3E%3CBR%20%2F%3EIs%20there%20a%20way%20to%20petition%20to%20join%20the%20beta%3F%3CBR%20%2F%3E%3CBR%20%2F%3EFailing%20that%2C%20is%20it%20understood%20that%20the%20Disable-AzSecurityAdvancedThreatProtection%20cmdlet%20is%20not%20expected%20to%20disable%20billing%20for%20the%20ATP%20feature%3F%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2757923%22%20slang%3D%22en-US%22%3ERe%3A%20Possible%20to%20Disable%20Defender%20on%20individual%20Storage%20Accounts%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2757923%22%20slang%3D%22en-US%22%3EThere%20is%20something%20else%20you%20need%20to%20do%20before%20running%20that%20cmdlet.%20Can't%20disclose%20all%20details%20publicly%20yet.%20Let%20me%20double%20check%20if%20this%20preview%20is%20still%20open%20for%20new%20participants.%3C%2FLINGO-BODY%3E
New Contributor

Hi folks,

 

The gist is that we have Azure Defender enabled at a Subscription level.  With that comes Advanced Threat Protection for Storage Accounts which is charged per transaction within those Storage Accounts.
 
We have four storage accounts out of 176 that are very highly transactional and the monthly billing for Advanced Threat Protection is close to $1,000.  They are internal storage accounts with very limited public exposure so we are not worried about threats within those transactions.  
 
Our ideal scenario would be to keep Defender enabled at the subscription level for all of our Storage accounts and all future storage accounts but not be billed for (or use) Advanced Threat Protection.  It seems like this cmdlet:
 
 
Should do the job, but it does not.  Either it does not disable ATP or it does not disable the billing.  In either of those cases it does not do what we need.
 
After 2.5 months or trying to work through it the only option I have been given is to disable Defender at the Subscription level for all of our Storage Accounts, and then re-enable the 172 storage accounts that we do want Defender for individually via PS.  That will and does work, but it will require overhead on our part to ensure they all stay enabled and that any future accounts are enabled by the creator and none get missed.  
 
Do we have any other avenues to suppress Advanced Threat Protection on a subset of accounts within a Subscription?  
8 Replies
This option to selectively disable Defender for certain storage accounts is currently being tested (closed private preview) and will likely be released later this year. No solid ETA though.
Thank you Stanislav,

Is there a way to petition to join the beta?

Failing that, is it understood that the Disable-AzSecurityAdvancedThreatProtection cmdlet is not expected to disable billing for the ATP feature?
There is something else you need to do before running that cmdlet. Can't disclose all details publicly yet. Let me double check if this preview is still open for new participants.
i am interested too for my customers.
Hi there, we'd also be interested in testing this feature. We are currently using SAs for FSLogix which are generating significant Defender costs.
We will add a guidance how to exclude certain accounts to our official documentation soon. Once it's there I will let you also know here. Thank you.
best response confirmed by CSP_MO (New Contributor)
Solution

We do not recommend excluding storage accounts from the Azure Defender, but If you want to perform cost optimization and you are considering the exclusion of specific storage accounts that are characterized with high traffic from the Azure Defender threat protection (e.g. storage accounts that are not open to the internet and do not contain sensitive data), it is possible to estimate the Defender for Storage costs first by following the blog post here.

 

To exclude specific storage accounts from Azure Defender, follow the following steps:

Step 1:

Enter the Tags section from the storage account(s) menu, and assign the following tag for the desired account(s) you would like to exclude:

Name

AzDefenderPlanAutoEnable

Value

off

After assigning the Tag name and value, click Apply.

It should look like the screenshot below after applying:

StanislavBelov_0-1634059256807.png

The tag excludes the account from getting updates from the subscription level enablement policy, these updates that occurs daily (If required, you can find here more information on assigning tags)

 

Step 2:

Disable "Azure Defender" on the desired accounts(s) by performing one of the following actions:

 

Option A (PowerShell command):

Run the following command in PowerShell on the relevant resource(s):
Disable-AzSecurityAdvancedThreatProtection -ResourceId <resourceId>

(the cmdlet is documented here)

 

Option B - Enable/Disable on the account level (from the Azure Security Center portal):
Security Center ➡ Pricing & settings ➡ Select the desired subscription ➡ Toggle Storage off/on (and click Save)

 

Thank you Stanislav!

Totally agree that we don't want to disable Defender for these accounts either, but we were running up $30 - $50 per day in Threat Protection because of how transactional the storage accounts were.
www.000webhost.com