Skip importing groups during Office 365 user provisioning
While federating Office 365 into Okta, you can choose to skip importing user groupsGroups allow you to organize your end users and the apps they can access. Assigning apps to large sets of end users is made easier with groups. and group memberships into Okta. This allows you to focus initially on the user provisioning and take care of group assignments later in the deployment process. It is helpful if your organization has multiple Office 365 domains and tenants that need to be federated in Okta.
To skip the import, on the Office 365 AppAn abbreviation of application. Essentially, it is a web-based site used to perform any number of specific tasks, and requires authentication from end users by signing in. > Provisioning > API Integration tab, clear the option to import groups. The option is selected by default.
|If "Import Groups" is||What Happens|
|Selected||Default option. All usersIn Okta literature, we generally refer to "users" as the people who serve as Okta administrators. When we refer to "end users" we are generally referring to the people who the administrators serve. That is, those who use Okta chiclets to access their apps, but have no administrative control. and groups are imported into Okta while federating the Office 365 domainA domain is an attribute of an Okta organization. Okta uses a fully-qualified domain name, meaning it always includes the top-level domain (.com, .eu, etc.), but does not include the protocol (https)..|
|Not selected||Users and groups are not imported during the domain federation. Any users and groups belonging to the domain and already imported in Okta are deleted. All associated app assignment policies are lost. Any future on-demand or scheduled imports only import users, not groups.|