How to fix Correlation ID: a451ce2a-6780-4b6a-a0bf-4e1c26441397

Question

How to fix Correlation ID: a451ce2a-6780-4b6a-a0bf-4e1c26441397

Ntokozo Simelane 10

Correlation ID: a451ce2a-6780-4b6a-a0bf-4e1c26441397 how to fix this?

When i try to log it says error what what

Emi Zhang-MSFT 30,016 Reputation points Microsoft External Staff

2024-04-04T01:23:02.4766667+00:00

Hi,

What product do you get an error message when you log in?
Ntokozo Simelane 10 Reputation points

2024-04-05T10:51:59.4266667+00:00

Correlation Id: 60aa035d-0a4c-4820-8eab-7c2a192a99a6

Timestamp: 2024-04-03T12:33:55.000Z

DPTI: cdc7b8e05a24b07c407e1820ba473a10fb4fa24a3c46e6956f0df4df3f3af6fa

Error Tag: 657rx

Error Code: 2148073494
Deleted

This comment has been deleted due to a violation of our Code of Conduct. The comment was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.
MOSTAFAFAROKHI 5 Reputation points

2025-04-30T01:33:01.63+00:00
Error Code: 2148073494

This decimal code corresponds to:

Hexadecimal: 0x80090006

Meaning: NTE_BAD_KEY — The key is invalid or not found.

This is a Windows cryptography error, commonly encountered in apps or services that depend on certificates, tokens, or encryption keys — such as Microsoft 365, Azure, Power Apps, or SharePoint.

Likely Cause

This error typically happens when:

A certificate used for authentication is missing, expired, or corrupted.

A token or session has expired or can't be decrypted due to a key mismatch.

The app or service can't access a cryptographic provider (e.g., Windows Key Store or Azure Key Vault).

Common Scenarios

In Power Apps or Power Automate: This happens when a custom connector, HTTP action, or authentication method depends on a certificate or token that’s no longer valid.

In SharePoint or Azure: A service principal or app registration may be misconfigured.

In Teams apps or embedded web parts: A token may fail to validate due to missing permissions or wrong scope.

What You Can Do

As a User:

Sign out and back into the app or service.

Clear browser cache or try incognito/private mode.

Try using a different browser or device.

Contact your IT admin with the full error (Correlation ID, Timestamp, Error Code).

As an Admin or Developer:

Check the Correlation ID in logs (e.g., Azure Monitor, SharePoint ULS, or Dataverse).

Verify authentication setup:

If using a certificate: ensure it's still valid and accessible.

If using OAuth tokens: verify token lifetimes and scopes.

Review key storage or cryptography settings (Key Vault, LocalMachine store, etc.).

Re-register the app or connector if needed.

1 answer

Your answer

Emi Zhang-MSFT 30,016 Reputation points Microsoft External Staff

2024-04-04T01:23:02.4766667+00:00

Hi,

What product do you get an error message when you log in?
Ntokozo Simelane 10 Reputation points

2024-04-05T10:51:59.4266667+00:00

Correlation Id: 60aa035d-0a4c-4820-8eab-7c2a192a99a6

Timestamp: 2024-04-03T12:33:55.000Z

DPTI: cdc7b8e05a24b07c407e1820ba473a10fb4fa24a3c46e6956f0df4df3f3af6fa

Error Tag: 657rx

Error Code: 2148073494
Deleted

This comment has been deleted due to a violation of our Code of Conduct. The comment was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.
MOSTAFAFAROKHI 5 Reputation points

2025-04-30T01:33:01.63+00:00

Error Code: 2148073494

This decimal code corresponds to:

Hexadecimal: 0x80090006

Meaning: NTE_BAD_KEY — The key is invalid or not found.

This is a Windows cryptography error, commonly encountered in apps or services that depend on certificates, tokens, or encryption keys — such as Microsoft 365, Azure, Power Apps, or SharePoint.

Likely Cause

This error typically happens when:

A certificate used for authentication is missing, expired, or corrupted.

A token or session has expired or can't be decrypted due to a key mismatch.

The app or service can't access a cryptographic provider (e.g., Windows Key Store or Azure Key Vault).

Common Scenarios

In Power Apps or Power Automate: This happens when a custom connector, HTTP action, or authentication method depends on a certificate or token that’s no longer valid.

In SharePoint or Azure: A service principal or app registration may be misconfigured.

In Teams apps or embedded web parts: A token may fail to validate due to missing permissions or wrong scope.

What You Can Do

As a User:

Sign out and back into the app or service.

Clear browser cache or try incognito/private mode.

Try using a different browser or device.

Contact your IT admin with the full error (Correlation ID, Timestamp, Error Code).

As an Admin or Developer:

Check the Correlation ID in logs (e.g., Azure Monitor, SharePoint ULS, or Dataverse).

Verify authentication setup:

If using a certificate: ensure it's still valid and accessible.

If using OAuth tokens: verify token lifetimes and scopes.

Review key storage or cryptography settings (Key Vault, LocalMachine store, etc.).

Re-register the app or connector if needed.

Answer 1

Clear Browser Cache and Cookies: If you're using a web browser, clearing the cache and cookies can resolve many login issues.
Try Incognito/Private Mode: Open a private browsing window and attempt to log in. This can help determine if extensions or cached data are causing the problem
Use a Different Browser or Device: Sometimes, browser-specific issues can prevent successful logins. Trying a different browser or device can help isolate the problem.
Check Internet Connection: Ensure you have a stable internet connection, as connectivity issues can interfere with authentication processes.
Sign Out and Sign Back In: If you're already signed in on another device or browser, sign out completely and then attempt to sign in again
Contact Support with Correlation ID: If the issue persists, contacting Microsoft Support and providing them with the Correlation ID can help them trace the problem in their logs and provide a solution.

Share via

How to fix Correlation ID: a451ce2a-6780-4b6a-a0bf-4e1c26441397

1 answer

Your answer