Editing synchronized user actions

When you edit synchronized user attributes in CoreView, you can update both on-premises (Active Directory) and cloud (Entra ID) properties in a single management action. To avoid confusion if attribute values sometimes appear temporarily blank or mismatched during updates, it helps to understand how synchronization works between CoreView, Microsoft Entra Connect, and your directory sources.

How synchronization works

• Immediate changes in CoreView
  When you edit both on-premises and cloud properties for a user, CoreView writes the changes right away. Updated values are immediately visible in the CoreView UI and reports.
• Cloud attribute changes: temporary impact on on-premises values
  Editing a cloud-only property triggers a partial import, instantly updating that field. During this process, related on-premises attributes may appear temporarily blank in CoreView—this is normal and the on-prem value is not lost.
• On-premises attribute changes: awaiting Entra Connect
  Changing an on-premises attribute requires synchronization from Active Directory to Entra ID using Microsoft Entra Connect (typically within 30 minutes). After this completes, CoreView’s next import restores the correct on-premises value in the UI and reports.

Synchronization flow: step by step

1. Edit the user and modify on-premises and/or cloud attributes in CoreView.
2. CoreView saves your changes and updates its UI immediately.
3. If a cloud attribute is changed, CoreView’s partial import updates that value, but may temporarily blank the related on-prem attribute.
4. Microsoft Entra Connect synchronizes changes from AD to Entra ID (usually within 30 minutes).
5. CoreView’s next import completes the process by showing the latest on-premises attribute alongside cloud properties.

Attributes affected by synchronization

Edits to the following user attributes in any synchronized management action will trigger the flow described above:

Identity and authentication

• First Name
• Last Name
• Display Name
• Employee ID
• Employee Number
• On-Premises Account Expiration Date
• Account Never Expires

Personal information

• Company
• Office
• Title
• Department
• Manager
• Street Address
• City
• State
• Postal Code
• Country
• Mobile Phone
• Fax Number

Extension attributes (on-premises)

• Extension Attribute1
• Extension Attribute2
• Extension Attribute3 … (typically up to Extension Attribute15, as defined by your AD schema)

Examples of actions triggering synchronization

• Editing a synchronized user property
• Assigning a template to a user (with sync fields)
• Any workflow action that updates synchronized fields