All versions of Windows currently supported by Microsoft.Users must be able to reach domain controllers.All end users must be assigned to the Office 365 instance associated with their specific domain.All Office 365 end users must have valid licenses.See Microsoft doc: Prepare to provision users through directory synchronization to Office 365. The Office 365 application username can be configured to map any AD attribute. The user's Active Directory UPN must match the Office 365 UPN.See Microsoft doc: Delegating Authority to Modify SPNs. Permissions in Active Directory to configure a Service Principle Name (SPN).Active Directory domain(s) integrated with your Okta org.Using Okta as an identity provider, once your end users have logged into a domain-joined Windows machine, they are automatically signed into Office 365 applications. Okta silent activation for Microsoft Office 365 provides a seamless experience for accessing Microsoft Office on shared workstations or VDI environments. If you have implemented the Early Access version of this feature prior to the 2019.09.0 release, refer to the instructions in Office 365 Silent Activation: Old Implementations. The steps in this topic apply to orgs that implemented this feature for the first time after Septem(after the 2019.09.0 release).
0 Comments
Leave a Reply.AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |