Two ATA feature requests - input?

Brass Contributor



An ATA customer with 60 000 seats has two new feature requests for ATA. I’ve told them that while ATA is still officially supported, Azure ATP is where the focus is, and it may be challenging to get new features added to ATA, but it doesn’t hurt to ask.


They will formally submit a Design Change Request via their TAM/SDM, but I wanted to see if anyone here has valuable input before that.


One of their requirements is MFA for accessing the portal, which is not possible today (see discussion here). We see at least two ways for this:

  • Support in ATA for federated login (i.e., forcing MFA on the Identity Provider side)
  • Adding native support for MFA/smartcard in ATA Center

The other is Group Managed Service Accounts (gMSA).

Today, the ATA Gateway service can run with a gMSA (at least according to the release notes of v1.8, but not documented anywhere else). But they want the ATA Center service to also run with a gMSA.


Again, not really questions, more asking for feedback/input before they formally submit a formal Design Change Request.



3 Replies

Hi  @TomAafloen 


gMsa is supported for running the  gateway itself instead of local service (although the value of that is really low, so not sure why anyone will want to do that).

it is not supported instead of using the AD account in the config page, (it is supported for AATP though!)


They are welcome to submit any feedback, but the chances of those happening for ATA at this point are very low.


I strongly advise them to check out AATP instead of ATA as it will give such a large customer much more value compared to ATA.

@Eli Ofek 

Yes, I have talked about AATP, but it's a licensing thing at the moment. It may be relevant in the future.


Can you clarify what is supported in AATP? Do you mean running the Azure ATP Sensor service with a gMSA, instead of adding a Directory Services user account in the AATP Configuration?

@TomAafloen  The service is still running as a virtual service account (local service), but in the config page which until recently you had to enter username and password, you can now just enter a gmsa account without password, so no need to manage this account any more with password replacements etc...