Your customer is currently using Directory Importer with Active Directory (AD) to provision users to...

[: The correct approach for provisioning users from different companies that use various directory services is supported by Netskope’s capabilities to integrate with multiple identity providers and directory services, as outlined in their documentation and community resources12., , Netskope supports multiple identity sources at the same time.In this scenario:, Company A (Active Directory):You can deploy additional Directory Importer (DI) instances to connect to separate AD forests or domains. Netskope supports multiple DI connectors., Company B (Azure AD):Azure AD provisioning uses SCIM, which is fully supported alongside DI., Company C (Okta Universal Directory):Okta also uses SCIM, and Netskope allows more than one SCIM integration simultaneously., Therefore, the customer can onboard all three companies without conflict., , , Why the other options are incorrect, A. Users from Company B and C cannot be provisioned because customer is already using AD Importer.❌ Incorrect — SCIM integrations can coexist with Directory Importer., B. Either Company B or C cannot be provisioned because only one SCIM solution is allowed.❌ Incorrect — Netskope supports multiple SCIM connectors., D. Company A users cannot be provisioned because the customer is already using AD Importer with another AD environment.❌ Incorrect — Multiple DI instances can be deployed for multiple AD environments., , ]