John Lockie

Members
  • Posts

    6
  • Joined

  • Last visited

Reputation

0 Neutral

About John Lockie

  • Rank
    Member
    Member
  1. Did a little digging and found this....looks like Microsoft decided to pseudonymize user-level info starting 9/1/21. They announced this on 8/30/21 (LOL!). https://techcommunity.microsoft.com/t5/microsoft-365-blog/privacy-changes-to-microsoft-365-usage-analytics/ba-p/2694137
  2. Ok - that fixed it. I think Microsoft may have changed something automatically at some point. FIX: go to admin.microsoft.com, sign in as global admin, go Settings > Org Settings > Reports Uncheck the box "Display concealed user, group, and site names in all reports This fixed the names in LM as well.
  3. So yes, Microsoft has changed something. LogicMonitor is using the Reporting module in GraphAPI to "getSharePointSiteUsageDetails" which is served by the Usage Reporting data in Microsoft 365 admin center. Even that data is completely masked on purpose. I have a feelign Microsoft changed this. So now you have to explicity tell your tenant to allow this type of data to be visible within reports. Info here: https://docs.microsoft.com/en-US/microsoft-365/admin/activity-reports/activity-reports?view=o365-worldwide#show-user-details-in-the-reports I am trying this now and will report back....
  4. Yeah I spoke to support today - this is very much not good. Makes the entire monitoring tool for SharePoint useless. Support said: "This is the response we see from Microsoft showing the GUID as the name rather than the site. We pull this data from a CSV generated within the O365 environment, so if the names in that CSV are the GUIDs we would expect them to show up here as GUIDs" What's very interesting is that it used to work just fine. Initially we were able to poll the data, and then we accidently changed collectors to use one of our Linux collectors and didn't realize that broke it. We set the collector back and then it suddenly updated all our sharepoint sites with these GUIDs 😮
  5. I was looking into why we have no data through our O365 SaaS monitoring resource, and discovered that you cannot use a Linux collector to collect data from O365 because it requires powershell. Despite not collecting any data, up until that point it had at least parsed all our SharePoint Online sites by the site URL (i.e. "https://tenant.sharepointonline.com/sites/SITENAME"). So it was easy to search for sties we cared about....and easy to look at top 10 report, etc. (except that our data was missing due to using a Linux collector). Once I reconfigured the resource to use one of our Windows collectors it started getting data (sweet!), except now all our SharePoint Online sites are listed as GUIDs....!?!? What the heck? Do I just need to wait for this to fix itself? I did a "active discovery" as well as "force data source rematch" and no luck. << these used to be URLs that were easily readable/searchable.....
  6. I would like to monitor internal web applications, but we use Okta or AzureAD and in both cases there is a required authentication step. Has anyone figured out how to get around this or accommodate the login requests?