<iframe src="https://www.googletagmanager.com/ns.html?id=GTM-M74D8PB" height="0" width="0" style="display:none;visibility:hidden">
Loading
Skip to NavigationSkip to Main Content
System Status
Announcements
Announcements
Search
Search
Select Language
Knowledge Base
Knowledge Articles
Support Videos ↗
Documentation
Product Documentation ↗
Developer Documentation ↗
Product Release Notes ↗
Community
Events & Webinars
Okta Ideas ↗
Resources
Product Hub
Customer Success Hub
Product Release Update
Learning
Okta Learning ↗
Get Support
Open a Case
HomeCommunityForum
0D50Z00008G7V7pSAFOkta Classic EngineOkta Integration NetworkAnswered2024-04-30T17:00:11.000Z2015-09-02T21:35:01.000Z2018-08-12T04:16:49.000Z

j5v7c (j5v7c) asked a question.

Edited by varun.kavoori1.5210444522562532E12 September 5, 2018 at 1:20 AM
When is Dirsync required for Office 365
I  have a customer who is deploying O365. He'd like to use users' email/accounts with O365. He will be migrating completely off of on prem Exchange. Under what circumstances is dirsync required vs using Okta provisioning with password push?

 

Is there any loss in functionality, aside from not having all of the user attributes pushed to O365?

 

Will Okta/UM cause issues with Office Web application access? For example opening embedded spreadsheets in Sharepoint online/on prem, etc?

 

Original Author: Jose Fernadez, Sr. Systems Engineer, Okta
  • 3 answers
  • 884 views

  • j5v7c (j5v7c)

     

    There is loss of functionality if the customer is wanting to use the Lync & Skydrive Pro rich client integration with Office thick clients. These are not possible without DirSync.

     

    If your customer ONLY wishes to use the web version of Lync, Sharepoint, and office apps, then there would be no loss in functionality.  Most enterprise customers like the richer set of functionality present in the fat clients. So for them dirsync is a requirement.

     

    Original Author: Joseph Gazarik, Mgr, Expert Services, ISVs, Okta

     
    Expand Post
    Selected as Best

  • j5v7c (j5v7c)

     

    There is loss of functionality if the customer is wanting to use the Lync & Skydrive Pro rich client integration with Office thick clients. These are not possible without DirSync.

     

    If your customer ONLY wishes to use the web version of Lync, Sharepoint, and office apps, then there would be no loss in functionality.  Most enterprise customers like the richer set of functionality present in the fat clients. So for them dirsync is a requirement.

     

    Original Author: Joseph Gazarik, Mgr, Expert Services, ISVs, Okta

     
    Expand Post
    Selected as Best

  • Peter McCarthy (Customer)

    Thomas,

     

    It's been a few months since your last comment. We are using the Skype for Business (formerly Lync) local client with our Office 365 deployment. Is Dirsync/Azure AD Connect still required for it to work, at this point in time? If so, are you able to explain what specifically requires Dirsync/AADC?
    Expand Post

  • JohnN.03536 (Customer)

    I'd like to second this bump.  We are trying to remove it from the local environment if we don't need it.  We had DirSync offline for about a week using only Okta Provisioning and things 'seemed' to be going okay.  We're not using either at the moment pending the resolution of an issue we encountered with Okta Provisioning.
This question is closed.
Loading
When is Dirsync required for Office 365