Share via

AD Azure Connect installation - Response status code does not indicate suffess 403 (forbidden)

Michał Witwicki 6 Reputation points
2023-04-11T09:42:03.27+00:00

Hi, when installing AD Azure Connect I get an error message (Response status code does not indicate suffess 403 (forbidden)). The error appears at the very end during configuration. I have installed AD Azure Connect many times and there was no problem. Has anyone encountered this problem? Log output: [13:33:55.689] [ 28] [ERROR] Creation of connector ***.onmicrosoft.com - AAD failed. This may be due to replication delay. Retry timespan exceeded. NOT retrying. [13:33:55.689] [ 28] [INFO ] Task 'Configure AAD Sync' has finished execution [13:33:55.689] [ 20] [ERROR] System.Management.Automation.CmdletInvocationException: Response status code does not indicate success: 403 (Forbidden). ---> Microsoft.IdentityManagement.PowerShell.ObjectModel.SynchronizationConfigurationValidationException: Response status code does not indicate success: 403 (Forbidden). Obraz bez nazwy

Microsoft Security | Microsoft Entra | Microsoft Entra ID
0 comments

2 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Michał Witwicki 6 Reputation points
    2023-05-23T14:00:14.08+00:00

    Solution.

    The problem was the configuration of the network, more precisely, the traffic went out and came back with two different internet providers. After setting the traffic to one ISP, the problem disappeared.

    1 person found this answer helpful.
    0 comments
  2. Sandeep G-MSFT 20,921 Reputation points Microsoft Employee Moderator
    2023-04-17T08:24:44.3866667+00:00

    @Michał Witwicki

    This error message indicates that the creation of a connector for your Azure AD tenant has failed. This can occur due to a variety of reasons, such as replication delays or network connectivity issues. Here are some steps you can take to troubleshoot this issue:

    1. Check the status of your Azure AD tenant**1**. You can do this by going to the Azure portal and selecting Azure Active Directory. From there, you can check the status of your tenant and see if there are any issues that may be causing the connector creation to fail.
    2. Check your network connectivity. Ensure that your network is properly configured and that there are no issues with connectivity between your on-premises environment and Azure. You can check below article to get required ports and URL's
      https://learn.microsoft.com/en-us/azure/active-directory/hybrid/reference-connect-ports#table-2---azure-ad-connect-and-azure-ad
    3. Retry the connector creation. If the issue is due to replication delays, you can try to create the connector again after waiting for some time. You can also try to create the connector from a different location or network to see if that resolves the issue.

    Let me know if you have any further questions.

    Please "Accept the answer" if the information helped you. This will help us and others in the community as well.

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.