The administration of a hybrid deployment that connects on-premises Exchange Server with Exchange Online, enabling seamless integration and centralized control.
GoodResource I want to help you with this question.
If I understand you right you want to bypass ADFS on the mentioned apps.
That's possible but keep in mind that the authentication is based on the user object or the UPN in the ADFS. This means that the user can have the authentication status "federated" or "managed". If it is "managed", it is no longer redirected to ADFS and uses Azure authentication.
This scenario is also explained again here:
It is recommended to first test the new authentication flow with a test group and then migrate the remaining users step by step.
Normally, the Home Realm Discovery process would redirect the routing of a defined domain in ADFS directly back to ADFS authentication. However, the change ( via Azure AD Connect Wizard and Powershell) allows, for example, ******@domain.com to be assigned the status "managed" (through group assignment) and ******@domain.com to continue using ADFS authentication through the existing status "federated" and no group assignment.
In general, the command to change the authentication type is: Set-MsolDomainAuthentication -DomainName domain.com -Authentication Managed
You can also check with the PS Command "Get-MsolDomain" what the authentication state is for the users at that moment.
But please follow the steps of the staged migration process.
In short words, these are the necessary steps (for specific groups)):
- Enable & start Azure AD Connect Password Sync.
- Change domain from "Federated" to "Managed
- Test client access
In conclusion, yes, it is possible, but not on an app basis, but only for a specific user group.
If the reply was helpful, please don’t forget to upvote or accept it as an answer, thank you.