Microsoft has announced a change to their Office 365 address and url documentation that I believe will need to be taken into account on the O365 miner in MM.
Basically, they are phasing out the old documentation page, which I believe the miner uses today, and phasing in a REST based API for getting updates to this data.
Does anyone know if the authors of the current miner have plans to take this into account?
Solved! Go to Solution.
good news! we already introduced the Miner for the new API in the 0.9.48!
Bad news is that MSFT has changed the API some days ago, we will release an update today to support these changes.
Sorry, one quick followup question - Can I add the new api based miner, say off of prototype o365-api.worldwide-any, and have it input into the existing office365 ipv6/ipv4/url aggregators? Seems likely, but I just wanted to be sure.
I'm afraid the new API does not provide a method to extract the indicators for just the Teams application.
In the following page https://support.office.com/en-us/article/managing-office-365-endpoints-99cab9d4-ef59-4207-9f2b-3728e... you'll find details for the new API.
It is stated there that ... Valid items are Common,Exchange,SharePoint,Skype ... No specific ServiceArea for MS Teams
As per the following url both Skype and Teams are listed with the same service area display name. Hence can I use the same prototype o365-api.worldwide-skype for teams as well?
Thanks in advance,
Click Accept as Solution to acknowledge that the answer to your question has been provided.
The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!
These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the Live Community as a whole!
The Live Community thanks you for your participation!