Solution: Use a global administrator account that is not federated to configure Azure AD Connect. Does the solution meet the goal?

A company uses Azure AD Connect. The company plans to implement self-service password reset (SSPR).

An administrator receives an error that password writeback cloud not be enabled during the Azure AD Connect configuration. The administrator observes the following event log error: Error getting auth token

You need to resolve the issue.

Solution: Use a global administrator account that is not federated to configure Azure AD Connect. Does the solution meet the goal?
A . Yes
B . No

Answer: B

Explanation:

The proposed solution to use a global administrator account that is not federated to configure Azure AD Connect does not directly address the error message "Error getting auth token" described in the scenario, so it is unlikely to solve the issue.

To resolve this issue, you should verify that the Azure AD Connect server can authenticate to the Azure AD tenant using valid credentials. If authentication is successful, then you can investigate other possible causes such as network connectivity problems, misconfigured firewall rules, expired certificates, etc.

Therefore, the correct answer remains option B, "No".

Reference:

https://docs.microsoft.com/en-us/azure/active-directory/hybrid/tshoot-connect-authentication

https://docs.microsoft.com/en-us/azure/active-directory/hybrid/tshoot-connect-password-writeback

Latest AZ-720 Dumps Valid Version with 81 Q&As

Latest And Valid Q&A | Instant Download | Once Fail, Full Refund

Subscribe
Notify of
guest
0 Comments
Inline Feedbacks
View all comments