SOLVED

Not sure where we're using Office Discovery Service

%3CLINGO-SUB%20id%3D%22lingo-sub-286803%22%20slang%3D%22en-US%22%3ENot%20sure%20where%20we're%20using%20Office%20Discovery%20Service%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-286803%22%20slang%3D%22en-US%22%3E%3CP%3EJust%20received%20an%20email%20from%20MS%20telling%20me%20that%20Office%20Discovery%20Service%20is%20being%20retired%20and%20we%20need%20to%20make%20the%20necessary%20changes%20on%20our%20end.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI'm%20not%20sure%20where%2Fhow%20we're%20using%20this%20service.%20We%20do%20use%20Office%20365%2C%20primarily%20Exchange%2C%20but%20that's%20a%20pretty%20vanilla%20implementation%20with%20no%20integration%20with%20other%20services.%20We%20also%20have%20VMs%20on%20Azure%20that%20act%20as%20our%20AD%20machines.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EHow%20can%20I%20find%20out%20where%2Fhow%20we%20might%20be%20using%20this%20service%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-286803%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EOffice%20365%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-287951%22%20slang%3D%22en-US%22%3ERe%3A%20Not%20sure%20where%20we're%20using%20Office%20Discovery%20Service%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-287951%22%20slang%3D%22en-US%22%3E%3CP%3EThank%20you%20for%20your%20response!%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-287613%22%20slang%3D%22en-US%22%3ERe%3A%20Not%20sure%20where%20we're%20using%20Office%20Discovery%20Service%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-287613%22%20slang%3D%22en-US%22%3E%3CP%3ESam%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3BI%20received%20this%20message%20as%20well%20as%20did%20a%20couple%20of%20my%20clients.%26nbsp%3B%20Personally%2C%20I%20don't%20have%20any%20custom%20code%20in%20my%20tenant%2C%20and%20people%20seemed%20to%20only%20receive%20this%20message%20if%20Microsoft%20detected%20something%20in%20their%20Office%20365%20environment%20was%20using%20it.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EOne%20thing%20it%20*could*%20be%20is%20a%20third%20party%20add-in%2Fsolution%20you%20have.%20Some%20Office%20or%20Outlook%20Add-in%20could%20be%20using%20this%20Service%20in%20the%20background%20and%20you%20have%20no%20idea.%26nbsp%3B%20If%20this%20is%20the%20case%2C%20you%20shouldn't%20need%20to%20worry%20about%20it%20as%20the%20vendor%20of%20the%20product%20should%20be%20aware%20of%20it%20as%20well%20and%20updating%20their%20code%20to%20use%20the%20Graph%20instead.%20The%20only%20thing%20you%20may%20have%20to%20do%20is%20just%20make%20sure%20any%20third-party%20products%20you%20may%20be%20using%20are%20up-to-date.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EJust%20a%20thought%20I%20had%20when%20I%20received%20that%20message%20in%20my%20tenant%20as%20well%20and%20knew%20I%20didn't%20have%20any%20custom%20code%20I%20wrote%20in%20my%20environment%20that%20was%20using%20that%20service.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-286809%22%20slang%3D%22en-US%22%3ERe%3A%20Not%20sure%20where%20we're%20using%20Office%20Discovery%20Service%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-286809%22%20slang%3D%22en-US%22%3EIt%E2%80%99s%20replaced%20by%20using%20office%20graph%20for%20fetching%20different%20endpoints%20for%20mails%20calendars%2C%20files%20from%20onedrive%20etc..%3CBR%20%2F%3EIf%20you%20haven%E2%80%99t%20played%20around%20with%20API%E2%80%99s%20and%20stuff%20like%20that%20you%20probably%20don%E2%80%99t%20have%20to%20worry%3C%2FLINGO-BODY%3E
Highlighted
Occasional Contributor

Just received an email from MS telling me that Office Discovery Service is being retired and we need to make the necessary changes on our end.

 

I'm not sure where/how we're using this service. We do use Office 365, primarily Exchange, but that's a pretty vanilla implementation with no integration with other services. We also have VMs on Azure that act as our AD machines.

 

How can I find out where/how we might be using this service?

3 Replies
Highlighted
It’s replaced by using office graph for fetching different endpoints for mails calendars, files from onedrive etc..
If you haven’t played around with API’s and stuff like that you probably don’t have to worry
Highlighted
Best Response confirmed by Sam Uresin (Occasional Contributor)
Solution

Sam,

     I received this message as well as did a couple of my clients.  Personally, I don't have any custom code in my tenant, and people seemed to only receive this message if Microsoft detected something in their Office 365 environment was using it.

 

One thing it *could* be is a third party add-in/solution you have. Some Office or Outlook Add-in could be using this Service in the background and you have no idea.  If this is the case, you shouldn't need to worry about it as the vendor of the product should be aware of it as well and updating their code to use the Graph instead. The only thing you may have to do is just make sure any third-party products you may be using are up-to-date.

 

Just a thought I had when I received that message in my tenant as well and knew I didn't have any custom code I wrote in my environment that was using that service.

Highlighted

Thank you for your response!