Assign Office 365 to Users
At this point you have 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. in Okta and one or more DNS domains in Office 365 that are configured for Okta for federation. If you are not using Okta for the provisioning of users, you may also have users in Office 365. Now we need to tie all of this together. This is done by assigning the Office 365 application in Okta to users. This achieves two goals.
- Okta users with 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. assigned are able to login to Office 365 through Okta.
- If Provisioning is enabled in Okta:
- A user account will be created at the time of assigning the app. If a user already exists in Office 365, Okta will match the users up and maintain the relationship.
- A role and/or license will be assigned to the user in Office 365. This fully automates the ability to provision fully working accounts for end usersIn Okta literature, we generally refer to "end users" as the people who have their own Okta home page (My Applications), using chiclets to authenticate into all of their apps. End users do not have any administrative control. When we refer to "users" we are generally referring to the individual(s) who have administrative control. to log right into.
Assignment can happen in two ways, directly to a user account (individual assignment) or indirectly by using 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. (group assignment). The automation of role and license assignment is described at the end of this section.Top