I'm being denied access to the Log Analytics Demo environment all of a sudden after having access. How to fix?

Question

I'm being denied access to the Log Analytics Demo environment all of a sudden after having access. How to fix?

Anil Kumar 0

Helllo Team, I clicked on this link from a Microsoft Learn webpage (https://aka.ms/lademo) - KQL Queries practice sessions, and after signing into one of my accounts, I get this immediate error screen stating that I don't have access; this screenshot attached to this post. This is odd because everything was working perfectly normally earlier, email id: ******@outlook.com

Screenshot 2026-11-07 064024

Hemant Bharadwaj 370 Reputation points Microsoft Employee

2026-11-09T02:50:37.6333333+00:00
Likely cause: access to the demo environment is governed by scoped permissions/session routing, and your current sign-in context no longer matches the entitlement path for that demo tenant.

Open the demo link in an InPrivate session and sign in with the same account that previously had working access.

Clear cached Microsoft auth sessions (or use a separate browser profile) to avoid cross-tenant token reuse.

Verify whether the demo environment has changed access policy/time window and requires renewed authorization.

Capture exact UTC timestamp and correlation/request identifiers from the access-denied screen.

If access still fails, raise support through the Learn/Q&A channel with the correlation data so the environment owner can confirm entitlement mapping.

Validation checks:

Demo workspace opens without access-denied banner.

Query execution path is available after sign-in.

References:

Azure Monitor Log Analytics overview: https://learn.microsoft.com/azure/azure-monitor/logs/log-analytics-overview

Azure RBAC troubleshooting: https://learn.microsoft.com/azure/role-based-access-control/troubleshooting

Azure portal tenant switching: https://learn.microsoft.com/azure/azure-portal/azure-portal-tenant-switcher

“If you find this answer helpful, please upvote it. If this resolves your issue, please mark it as the accepted answer so that it can help others in the community.”

Your answer

Hemant Bharadwaj 370 Reputation points Microsoft Employee

2026-11-09T02:50:37.6333333+00:00

Likely cause: access to the demo environment is governed by scoped permissions/session routing, and your current sign-in context no longer matches the entitlement path for that demo tenant.

Open the demo link in an InPrivate session and sign in with the same account that previously had working access.

Clear cached Microsoft auth sessions (or use a separate browser profile) to avoid cross-tenant token reuse.

Verify whether the demo environment has changed access policy/time window and requires renewed authorization.

Capture exact UTC timestamp and correlation/request identifiers from the access-denied screen.

If access still fails, raise support through the Learn/Q&A channel with the correlation data so the environment owner can confirm entitlement mapping.

Validation checks:

Demo workspace opens without access-denied banner.

Query execution path is available after sign-in.

References:

Azure Monitor Log Analytics overview: https://learn.microsoft.com/azure/azure-monitor/logs/log-analytics-overview

Azure RBAC troubleshooting: https://learn.microsoft.com/azure/role-based-access-control/troubleshooting

Azure portal tenant switching: https://learn.microsoft.com/azure/azure-portal/azure-portal-tenant-switcher

“If you find this answer helpful, please upvote it. If this resolves your issue, please mark it as the accepted answer so that it can help others in the community.”