Suddenly getting "UserPrincipal doesn't have the key ID configured"

Question

I have an ongoing automation that executes various calls to the MS API
Recently I've started to fail with the following message below.
In this case, reauthenticating helped solve the issue but it seems like the 'refresh token' timed out for some reason even though this is an active instance.
Could help me take a look at the issue using the Correlation ID and try to figure out the source?

{'error': 'invalid_grant', 'error_description': "AADSTS135010: UserPrincipal doesn't have the key ID configured. Trace ID: f6c74d4e-dbe3-4b44-a205-bf76c8a49700 Correlation ID: 5a9d7e8c-b333-4c10-9b0b-68e207087a1a Timestamp: 2024-09-10 15:56:18Z", 'error_codes': [135010], 'timestamp': '2024-09-10 15:56:18Z', 'trace_id': 'f6c74d4e-dbe3-4b44-a205-bf76c8a49700', 'correlation_id': '5a9d7e8c-b333-4c10-9b0b-68e207087a1a'}

Answer 1

Hi @itay4

According to the documentation, try reverifying or creating a new connection. For details, see the documentation.

Hope this helps.

If the reply is helpful, please click Accept Answer and kindly upvote it. If you have additional questions about this answer, please click Comment.

Answer 2

Hey @Anonymous thx for the quick response.
I already found that article and a fix for the issue.
What I'm trying to figure out is why did it happen in the first place?

Answer 3

Any idea? @Anonymous