Documentation
    {{docApp.userSession.userId}}
    {{docApp.userSession.userName}}
    {{docApp.userSession.email}}
    Issuer : {{docApp.userSession.issuerInstance}}
    Expires : {{new Date(docApp.userSession.validUntil).toLocaleDateString()}}

{{docApp.title}}

{{docApp.description}}

How can we help?

{{docApp.searchError}}

{{docApp.searchResultFilteredItems.length}} results for: {{docApp.currentResultsSearchText}} in {{docApp.searchFilterBySpecificBookTitle}}

You have an odd number of " characters in your search terms - each one needs closing with a matching " character!

{{docApp.libraryHomeViewProduct.title || docApp.libraryHomeViewProduct.id}}

{{docApp.libraryHomeViewProduct.description}}

  1. {{book.title}}

{{group.title || group.id}}

{{group.description}}

  1. {{book.title}}

{{group.title}}

{{book.title}}
More...

Scheduling

You can schedule the User Import - Azure utility to run, with any of the documented command line arguments, from within the Windows Task Scheduler.

Important

Do not schedule your imports to run during the instance update window, as the imports may fail or act in an unexpected manner if the instance installs updates during this time.

The update windows can be found in the Continuous Delivery document.

There are several caveats that should be considered when scheduling this utility using the Windows Task Scheduler:

  • Ensure the user account running the task has rights to azure_user_import.exe and the containing folder. This is catered for automatically by Windows if the utility is stored and run from the service account user profile folder, as per the installation instructions.
  • Ensure the user account running the task is the one who performed the first run of the tool on the host computer, as per the first run instructions.
  • Make sure the Start In parameter contains the folder where the executable resides.

Warning

If you do not have the value of Start In set to the folder where the executable resides, then the task will not complete and will eventually time out in your scheduler. This is because the import utility cannot detect the file that contains your instance credentials, and is interactively prompting for these to be provided.

  • Version {{docApp.book.version}}
  • Node {{docApp.node}} / {{docApp.build}}
In This Document