How to know if Exchange oAuth Metadata is updated?

Louis CI Lo 65 Reputation points
2023-09-07T06:49:46.53+00:00

Hi,

 

I have an environment with Exchange 2013 hybrid coexistence with Exchange 2019 now. oAuth is enabled.

 

I am suspecting the current environment, servers won't refresh the oAuth Metadata themselves. Are there any logs I can trace that? What event ID indicate the metadata is updated?

Firstly, I noticed this issue when End user outlook 2019 keep prompting M365 login, it keeps to prompt no matter enter right credential or not. And after I use command: Set-AuthServer -RefreshAuthMetaData, problem solved. But from my understanding this metadata should be refreshed automatically.

Thanks and regards

Exchange Exchange Server Management
Exchange Hybrid management
0 comments No comments
{count} votes

Accepted answer
  1. Yuki Sun-MSFT 41,376 Reputation points Moderator
    2023-09-08T02:41:02.71+00:00

    Hi @Louis CI Lo ,

    I tried searching a lot but so far haven't found useful information about how to know Exchange oAuth Metadata is updated. Haven't' seen in any document stating if this could be traced by any logs or event id, either. But I'd recommend have a look at the event viewer right after you run the command to see if a relevant event could be recorded out there.

    Regarding your concern about whether this metadata is refreshed automatically, I've also done much research but didn't find evidence which can prove this.

    However, found an earlier thread which also mentioned that the outdated oAuth Metadata required to be manually updated using the command Set-AuthServer -RefreshAuthMetaData
    User's image

    Then I went through the document which includes the explanation of the RefreshAuthMetadata switch, it says "The RefreshAuthMetadata switch specifies whether Exchange should refresh the auth metadata from the specified URL. ", while doesn't mention anything about if normally the refresh should occur automatically or use any wording like "force refresh" which to some degree might indicate usually it is done automatically.

    So taken in the round, I am assuming this could be normal that we need to manually refresh the auth metadata using the aforementioned command. And in this case, personally I would suggest trying to create a scheduled task in your environment so that this command can be run backend periodically.


    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.

    1 person found this answer helpful.

0 additional answers

Sort by: Most helpful

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.