This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(185.6, 9%, 27%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EDD%3C/text%3E%3C/svg%3E)
We just took over a hybrid Exchange 2016/O365 mail environment & are on a learning curve....
Starting on or after approx. 3-18-2023 several users (lets say 12 out of about 600+) starting getting a message stating "Allow this website to configure ExchangeGuid+<useronlinearchiveGUID>@<domain.com>". Regardless of whether they click "Allow" or "Cancel" and/or click "Don't ask..." the message still pops up periodically and/or when launching Outlook & users Outlook behaves normally with the exception of the periodic message.
The only maintenance/change on the on-prem 2016 Exchange was we applied Security Update for Exchange Server 2016 Update 23 (KB5024296) & rebooted both mailbox servers on 3-16-23.
Looking at the Outlook Connection Status (CTRL-right-click Outlook system tray icon), the GUID in the message always correlates to an O365 online archive mailbox with an "Established" & the online archive mailbox can be browsed as expected. Sometimes it's the user's own online archive mailbox, sometimes it's a shared online archive mailbox.
All affected users & mailboxes are O365
All online archive mailboxes are O365
Clients are Outlook 2016 and current (2302/16130.20306)
Note that we have not run HCW after the update/reboot. Being new to the environment we're not sure whether this would help or is applicable given the behavior.
My apologies for the messy screen shots but you get the idea hopefully.
It really doesn't make any sense why it would only apply to online archive mailboxes & we're out of ideas.
Any suggestions?
-Dave
We've also tried suppressing the message with no luck (https://learn.microsoft.com/en-us/outlook/troubleshoot/connectivity/how-to-suppress-autodiscover-redirect-warning)
Additionally, we also gave the on-prem Exchange 2016 mailbox servers another reboot in addition to our load balancer - no change.
So oddly enough this problem just went away without any action on our part. We're blaming MS & O365.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(284.8, 17%, 37%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EYS%3C/text%3E%3C/svg%3E)
Hi @Dave Dicken ， Glad to see that the issue has gone away automatically and thanks for sharing the news here :-)
Hi @Dave Dicken ，
Regardless of whether they click "Allow" or "Cancel" and/or click "Don't ask..." the message still pops up periodically...
What if launching Outlook as administrator and then click "Don't ask..." when the message prompts?
Note that we have not run HCW after the update/reboot.
According to the official blog below, the recommended practice is to re-run the HCW if you changed the auth certificate after installing the March 2023 SU:
Released: March 2023 Exchange Server Security Updates
If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.
@Yuki Sun-MSFT I see that it specifically calls for running the HCW if we changed the auth certificate. Since I'm not sure what that is I'm assuming we didn't update it. Would you recommend still running the HCW? We're thinking that it can't hurt. If so, is there any risk running it? Is there any possibility of losing any connectors or anything of that nature? My bad experiences with Exchange 2010 & edge servers & how those connectors were notorious for getting deleted when we ran anything that touched those subscriptions. Right now we are somewhat on hold as our IT director would rather live with the messages vs the possibility of wrecking anything further.
Hi @Dave Dicken ，
In most cases, rerunning HCW won't harm anything, especially if you don't have any customized connecters configured in your environment. But each operation comes along with risks, so if it's ok to live with this message, keep it as it is could be the safest choice at present.