we received this mail over the weekend but cant find an answer in any documentation. Can anybody help clarifying what this means?
Thank you all,
This is an ongoing issue that our team is actively investigating. The following article will be updated once a resolution is found. - Advisory: Sophos Central - Some customers are seeing a Medium alert…
Same here, would be interesting what the root cause of this is, and what the impact
This just seems to be a prompt to set up AD sync, rather than an actual issue.
Well, AD Sync is set up since a year and I checked it this morning because that was my thought exactly. It synced twice today already so this seems not to be a problem.
Hi Ben,Thank you for reaching us, By any chance are there any recent changes on your API settings recently? You may follow this documentation for the steps to check the permission on your API. Once validated you can proceed with acknowledging the alert on your central
Hi GlennSen,thanks for the link to the KB article. I have read the instructions and checked the permissions for the sync app. The permissions in Azure for Sophos Central Synchronization were already set correctly in our case before. Nevertheless, we received the notification by mail on Saturday and for the second time this morning.
Azure Sync in Sophos Central is working
What can we do?
Same here.Same two messages Also german system, if this makes any differnce for Sophos Central.
Having same issue (English system). Added in the new Graph API access Friday per the documentation. Getting "Microsoft API permissions are missing" alerts when it syncs successfully.
If all steps in the document mentioned by Glenn have been followed, but you're continuing to receive alerts regarding this API permission, I recommend selecting "Mark as Acknowledged" as shown in the KBA linked below.- https://support.sophos.com/support/s/article/KB-000043897?language=en_US
If this continues to pose issues for you, please let us know by opening a support case so that we can investigate further.
Adding "us" to the list of people seeing this issue with seemingly no basis for the error.
We also got the alert and it looks like sophos also sent out some self central emails to users