We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
In December (ETA) Microsoft Defender for Cloud is grouping together all containers related plans into a single one.
Azure Defender for Kubernetes & Azure Defender for container registries will become a new plan of Microsoft Defender for Containers.
This is detailed further on the product announcements here: https://docs.microsoft.com/en-us/azure/defender-for-cloud/upcoming-changes#container-security-features-to-be-grouped-under-defender-for-containers
We will need to make the relevant policy changes to accommodate this change, once announced as GA by Microsoft Defender for Cloud.
Policy Details
THIS CAN ONLY BE DONE ONCE THE GA ANNOUNCEMENT IS MADE BY THE MICROSOFT DEFENDER FOR CLOUD TEAM
The text was updated successfully, but these errors were encountered:
This is now GA https://docs.microsoft.com/en-us/azure/defender-for-cloud/release-notes#microsoft-defender-for-containers-plan-released-for-general-availability-ga
Sorry, something went wrong.
jtracey93
Successfully merging a pull request may close this issue.
In December (ETA) Microsoft Defender for Cloud is grouping together all containers related plans into a single one.
Azure Defender for Kubernetes & Azure Defender for container registries will become a new plan of Microsoft Defender for Containers.
This is detailed further on the product announcements here: https://docs.microsoft.com/en-us/azure/defender-for-cloud/upcoming-changes#container-security-features-to-be-grouped-under-defender-for-containers
We will need to make the relevant policy changes to accommodate this change, once announced as GA by Microsoft Defender for Cloud.
Policy Details
The text was updated successfully, but these errors were encountered: