Skip to page contentSkip to chat
ServiceNow support
    • Community
      Ask questions, give advice, and connect with fellow ServiceNow professionals.
      Developer
      Build, test, and deploy applications
      Documentation
      Find detailed information about ServiceNow products, apps, features, and releases.
      Impact
      Accelerate ROI and amplify your expertise.
      Learning
      Build skills with instructor-led and online training.
      Partner
      Grow your business with promotions, news, and marketing tools
      ServiceNow
      Learn about ServiceNow products & solutions.
      Store
      Download certified apps and integrations that complement ServiceNow.
      Support
      Manage your instances, access self-help, and get technical support.
Microsoft AZURE provisioning only targets sys_user and optionally sys_group tables - Support and Troubleshooting
  • >
  • Knowledge Base
  • >
  • Support and Troubleshooting (Knowledge Base)
  • >
  • Microsoft AZURE provisioning only targets sys_user and optionally sys_group tables
KB0655991

Microsoft AZURE provisioning only targets sys_user and optionally sys_group tables


10034 Views Last updated : Jul 24, 2025 public Copy Permalink English (Original)
  • English (Original)
  • Japanese
KB Summary by Now Assist

Issue

Microsoft AZURE does not create records in ServiceNow tables other than sys_user, or optionally sys_group. You might want to map other tables like location, company, etc.

Cause

The provisioning service does resolve references between sys_user records and other ServiceNow tables, but it does not create records in other tables like cmn_location.

Resolution

Microsoft Azure provisioning is not a ServiceNow product. Please contact Microsoft for specific questions.

The typical Azure user provisioning flow is as follows:

  1. Azure AD sync service looks up assigned users in scope for provisioning in Azure AD.
  2. If new users have been assigned or otherwise added to the scope since the last sync, the Azure AD sync service queries ServiceNow to see if those users exist.
  3. If a user does not exist in ServiceNow, a new user is created in the sys_user table.
  4. If a user does exist, then it is updated with any user attributes found to be out of sync.
  5. After the steps above have been completed, the Azure AD sync service queries for any ServiceNow reference attributes specified in the Azure AD sync attribute mappings.
  6. The Azure AD sync service then updates the user record with the reference attribute values.
     
    If location is configured as one of the target attributes to sync to in the attribute mappings, the sync service should be updating that field.
     
    The provisioning service does resolve references between a sys_user record and other ServiceNow tables, but it does not create records in other tables like cmn_location. 
 Warning: When dynamic creation is enabled, entering a nonexistent value in a reference field creates a new record on the referenced table instead of returning an error.

The world works with ServiceNow.

Sign in for more! There's more content available only to authenticated users Sign in for more!
Did this KB article help you?
Did this KB article help you?

How would you rate your Now Support digital experience?

*

Very unsatisfied

Unsatisfied

Neutral

Satisfied

Very satisfied

Very unsatisfied

Unsatisfied

Neutral

Satisfied

Very satisfied

What can we improve? Please select all that apply.

What are we doing well? Please select all that apply.

Tell us more

*

Do you expect a response from this feedback?

  • Terms and conditions
  • Privacy statement
  • GDPR
  • Cookie policy
  • © 2025 ServiceNow. All rights reserved.