Microsoft Defender for Servers and Cost Management and Billing

[artgola]

There is currently no way to itemize the total cost of Defender for Servers at the Virtual Machine level.

When The Defender for Servers Plan is enabled at the Azure subscription, billing for all servers in the subscription is rolled up to a total amount at the subscription. It is not possible in Cost Management and Billing to see the cost for the Defender for Servers Plan for a particular Virtual Machine resource or resource group.

[#2]

you can enable defender for servers only at subscription level..
to see estimated costs there is an workbook: defender for cloud > workbooks > price estimation > defender for servers

[#3]

@artgola 

Just wondering you are concern with Microsoft Defender for Server only, how about other common services such as network? if yes, how about an effective tag approach?

https://techcommunity.microsoft.com/t5/microsoft-defender-for-endpoint/how-to-use-tagging-effectivel...

[#4]

@artgola.
You are correct that when you enable Microsoft Defender for Servers at the Azure subscription level, the billing information is rolled up at the subscription level. However, if you need to see the cost for the Defender for Servers Plan for a particular Virtual Machine resource or resource group, you can use a workaround to estimate the cost distribution.

To get an estimation of the cost per VM, you can follow these steps:

1- Export the Azure Cost Management data: Navigate to the Azure Cost Management and Billing section in the Azure Portal. Select the "Cost analysis" option under "Cost Management." Set the desired date range, and group the data by "Resource." Then, click on "Export" to download the data in a format of your choice, such as CSV.
2- Calculate the usage: Open the exported data and identify the usage for the Defender for Servers Plan by filtering the data based on the 'Meter' or 'Meter Category' column. Calculate the total usage for Defender for Servers Plan across all VMs in the subscription.
3- Calculate the cost per VM: Divide the total cost for Defender for Servers by the total usage to find the cost per unit. Then, multiply this cost per unit by the usage for each individual VM to estimate the cost for the Defender for Servers Plan for each VM.
4- Group the costs by resource group: To view the cost distribution at the resource group level, you can aggregate the estimated costs for all the VMs within a resource group.

Please note that this method provides an estimation and may not be completely accurate. To get more granular cost data, you can provide feedback to Microsoft to request support for itemizing costs at the VM level in future updates of Azure Cost Management and Billing.

[#5]

Hi Team, Is any way to submit a feature request to view actual billing for Azure Defender for Cloud for each Resource Group separately?

[#6]

Hello @Abhaykainos
Yes, you can submit a feature request to the Azure Feedback Forum. The Azure Feedback Forum is a platform where customers can share their ideas, request new features, and provide feedback on existing Azure services. The Azure product team actively monitors and considers the feedback provided by users to improve their services.

To submit a feature request for Azure Defender for Cloud billing, follow these steps:

1. Visit the Azure Feedback Forum: https://feedback.azure.com/forums/34192--general-feedback
2. Click on the "Post a new idea…" button or search to see if a similar request has already been submitted.
3. If a similar request exists, vote for it to show your support. If not, create a new post by providing a descriptive title and detailed explanation of the feature request you'd like to see implemented.
4. Choose the appropriate category for your request. In this case, it might be "Security and Compliance" or "Billing and Subscriptions."
5. Click "Post idea" to submit your feature request.

Remember to provide as much detail as possible in your request, explaining the benefits and use cases of the feature you're proposing. This will help the Azure product team better understand your needs and prioritize feature requests accordingly.

Also, engage with the community and encourage others who share your interest in the feature to vote for your idea, as this can increase the likelihood that the Azure team will consider implementing the requested feature.