Managing security by using Microsoft Defender for Cloud
Microsoft Defender for Cloud was previously known as Azure Security Center and Azure Defender. I want to set some context around the reasoning and detail of the responsibilities that are split between Microsoft and the customer.
We previously spoke about advanced security features, such as reverse connect, which reduces the risk of exposing Virtual Desktop resources directly to the public network. We’ll now look at the security responsibilities and some of the Azure security best practices available.
Here are the security areas you’re responsible for in your Azure Virtual Desktop (AVD) deployment. Note that the value under the Customer responsibility column is Yes if the customer is responsible and No if Microsoft is responsible:
Security areas |
Customer Responsibility |
Identity |
Yes ... |