Requiring the Object ID be synced for user accounts will ensure a 1:1 mapping between Onspring and Azure and also serve as a flag that the user account in Onspring was created by OnspringAzureADSyncer. The flag can then be used by other features of the application to ensure that only account synced to Azure are being updated and that external accounts and internal but locally authenticated and managed accounts are not impacted.
The requirement would be listed in the README.md and would be checked during the validation set in the same way that using the Group sync checks for mapping the Object ID field.
Requiring the Object ID be synced for user accounts will ensure a 1:1 mapping between Onspring and Azure and also serve as a flag that the user account in Onspring was created by OnspringAzureADSyncer. The flag can then be used by other features of the application to ensure that only account synced to Azure are being updated and that external accounts and internal but locally authenticated and managed accounts are not impacted.
The requirement would be listed in the README.md and would be checked during the validation set in the same way that using the Group sync checks for mapping the Object ID field.