Forum Discussion
Audit log search error: "Fail to opt in, please refresh"
- Oct 29, 2019
Microsoft have confirmed a fix has been deployed! See below from the Microsoft engineer -
Please be informed that the fix has been deployed to customers that are receiving the alarm "Fail to opt-in, please refresh" on the Audit log search page. This alarm "Fail to opt-in, please refresh" can be ignored, as the search is not currently affected.
The fix has been checked, but it may still need 3 more weeks to be deployed fully to all data center servers
REGHA1205 Have you received any further updates, I am seeing this message constantly and refresh has no effect,
No further updates from Microsoft.
I will chase them again today.
- cra1901Oct 28, 2019Copper Contributor
If it's of any help to anyone, the message I received in responce to my ticket was:
Thanks for giving the workaround a short.
As pointed out in my previous email, there is a service degradation impacting Exchange Online audit log data search.(EX193067 and EX193722).
We sincerely apologize for any inconvenience this has caused you.
Please be assured this is currently been reviewed.
I will keep tabs on this and update you as soon as updates on this.
The Workaround mentioned was to connect to Exchange Online using PowerShell and run the Enable-OrganizationCustomization cmdlet. This was already enabled in our case.
- BenC187xOct 28, 2019Copper Contributor
I have had a reply from microsoft, just as I suspected....
Please be informed that our engineers are working towards achieving a resolution to the issue, and admins will be able to manage Audit Log Search, once the fix reaches their respective environments.
- BenC187xOct 29, 2019Copper Contributor
Microsoft have confirmed a fix has been deployed! See below from the Microsoft engineer -
Please be informed that the fix has been deployed to customers that are receiving the alarm "Fail to opt-in, please refresh" on the Audit log search page. This alarm "Fail to opt-in, please refresh" can be ignored, as the search is not currently affected.
The fix has been checked, but it may still need 3 more weeks to be deployed fully to all data center servers