Jump to content

New Azure Import Failure?

Recommended Posts

We are currently movijng from LDAP Import to Azure AD import, when we originally began we were using an older version of the Azure AD importer and any Dry Runs proved successful.


Unfortunately since updating to the latest azure import (using the same credentials mapped in the API) it fails to connect to the Azure Tenancy, Errror 404.


Is there anyone who can provide some insight as to if there is a difference in the newer versions of the Azure Import tool that may need addressing within Azure?



Link to comment
Share on other sites

  • 2 weeks later...

Based on our investigation this was due to an incorrect value for the "APIVersion" parameter in the JSON configuration file. The correct value for this parameter used with existing import tool versions is "v1.0". The documentation incorrectly advised to use "1.0", it was incorrect and this has now been rectified.

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Create New...