Blog Post
Containment Strategies for AI now available in Secure Now
"AI transformation will reward organizations that can move quickly and securely. The fastest path is not to treat security as a blocker or an afterthought. It is to establish a strong foundation early, reduce exposure proactively, and make readiness a continuous discipline."
"Containment"??!! - I want Disabled/Off by Default.
Isn’t this a difficult position to defend when Microsoft continues enabling AI agents across the Admin Center, Entra, and Microsoft Teams?
Where is the global, tenant-wide control that allows administrators to disable these capabilities by default? Security-conscious organizations should not have to hunt through multiple portals and settings to opt out individually. I work at mature organization, and we are not able to keep up with all of these changes, we even have a dedicated company that specializes is keeping us up to date as well.
How does this approach align with Microsoft’s Secure Future Initiative?
I have been trying to do so, let us enable when we wish. There are use cases for that and we gladly turn on after review, pushing everything on does not make any sense to me!
The "strong configuration" simplist solution is Disabled/Off by Default.