Using Group managed service accounts (gMSA) with Azure ATP

%3CLINGO-SUB%20id%3D%22lingo-sub-1125138%22%20slang%3D%22en-US%22%3ERe%3A%20Using%20Group%20managed%20service%20accounts%20(gMSA)%20with%20Azure%20ATP%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1125138%22%20slang%3D%22en-US%22%3E%3CP%3EThis%20is%20amazing%20news!%20Thank%20you%20very%20much!%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1121775%22%20slang%3D%22en-US%22%3EUsing%20Group%20managed%20service%20accounts%20(gMSA)%20with%20Azure%20ATP%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1121775%22%20slang%3D%22en-US%22%3E%3CP%3EHey%20everyone%2C%3C%2FP%3E%0A%3CP%3EBased%20on%20customer%20feedback%20and%20to%20improve%20overall%20security%20and%20compliance%20requirements%2C%20we%20will%20soon%20be%20introducing%20the%20option%20to%20use%20a%20more%20secure%20Group%20managed%20service%20account%20(gMSA)%20to%20connect%20Azure%20ATP%20sensors%20to%20your%20Active%20Directory%20forests%20alongside%20the%20existing%20standard%20read-only%20AD%20account.%3C%2FP%3E%0A%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20style%3D%22width%3A%20400px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F166476iD46E2B26BA9BA729%2Fimage-size%2Fmedium%3Fv%3D1.0%26amp%3Bpx%3D400%22%20alt%3D%22clipboard_image_0.png%22%20title%3D%22clipboard_image_0.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3EWhile%20we%20are%20getting%20ready%20with%20this%20release%20and%20the%20documentation%20on%20how%20to%20enable%20it%2C%20we%20strongly%20recommend%20verifying%20your%20Azure%20ATP%20sensors%20are%20updating%20correctly%20and%20that%20no%20%22%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fazure-advanced-threat-protection%2Fmonitoring-alerts%23sensor-outdated%22%20target%3D%22_self%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3ESensor%20outdated%3C%2FA%3E%22%20health%20alert%20has%20triggered.%3C%2FP%3E%0A%3CP%3EAs%20you%20might%20already%20know%2C%20we%20%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fazure-advanced-threat-protection%2Fatp-whats-new%23azure-atp-release-2104%22%20target%3D%22_self%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3Erecently%20introduced%3C%2FA%3E%26nbsp%3Ba%20change%20to%20how%20we%20manage%20sensor%20versions%20which%20means%20that%2C%20when%20connected%20to%20the%20Azure%20ATP%20cloud%20service%2C%20every%20existing%20or%20newly%20deployed%20sensor%20will%20update%20to%20the%20latest%20version%20either%20automatically%20or%20after%20the%20%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fazure-advanced-threat-protection%2Fsensor-update%23delayed-sensor-update%22%20target%3D%22_self%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3Edelayed%20sensor%20update%3C%2FA%3E%20period%20(72%20hours)%20has%20passed%20if%20that%20option%20is%20configured.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EOne%20final%20note%20to%20consider%20is%20that%20gMSA%20accounts%20are%20supported%20on%20Windows%20server%20version%202012%20and%20higher%2C%20which%20mean%20that%20if%20you%20still%20have%20domain%20controllers%20hosted%20on%20Windows%20server%202008%20R2%2C%20you%20should%20keep%20at%20least%20one%20standard%20AD%20account%20%3CU%3Ein%20addition%3C%2FU%3E%20to%20any%20new%20gMSA%20account%20on%20your%20%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fazure-advanced-threat-protection%2Finstall-atp-step2%22%20target%3D%22_self%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3EDirectory%20services%3C%2FA%3E%20configuration%20screen.%3C%2FP%3E%3C%2FLINGO-BODY%3E
Highlighted
Microsoft

Hey everyone,

Based on customer feedback and to improve overall security and compliance requirements, we will soon be introducing the option to use a more secure Group managed service account (gMSA) to connect Azure ATP sensors to your Active Directory forests alongside the existing standard read-only AD account.

clipboard_image_0.png

While we are getting ready with this release and the documentation on how to enable it, we strongly recommend verifying your Azure ATP sensors are updating correctly and that no "Sensor outdated" health alert has triggered.

As you might already know, we recently introduced a change to how we manage sensor versions which means that, when connected to the Azure ATP cloud service, every existing or newly deployed sensor will update to the latest version either automatically or after the delayed sensor update period (72 hours) has passed if that option is configured.

 

One final note to consider is that gMSA accounts are supported on Windows server version 2012 and higher, which mean that if you still have domain controllers hosted on Windows server 2008 R2, you should keep at least one standard AD account in addition to any new gMSA account on your Directory services configuration screen.

6 Replies
Highlighted

This is amazing news! Thank you very much!

Highlighted

@Or Tsemah 

Is this option available in all Tenants?  We provisioned our tenant last week and the gMSA option is not there to select.

Highlighted

@dobieg2002  This is a known bug that only happens to new tenants.

2 options:

1. Open a support ticket and the support engineer will create an internal request to turn this option on for you manually in the backend (make sure to give them your workspace id).

2. Wait for the version that will be deployed next week, which will auto fix the issue for everyone.

 

Eli

Highlighted

@Or Tsemah What is the recommended approach with a gMSA account when you have multiple domains in the forest. Can we use single gMSA created in forest root domain to use on all the child domains, or would you need a gMSA for each domain in the forest?

Highlighted

@JohanHeyneke , if you have full trust between all those domains, and all the DCs in the forest are granted permission to pull this gmsa account's password, then yes, you can work with a single gmsa.

Highlighted

@Eli Ofek Thanks for the quick response. This is great news.