[OMS] ‘Session Expired’ even if the user is working in the OMS portal


Just a short post on an OMS issue.

If you are working in the OMS portal and are getting despite of this a 'Session Expired' message, please make sure the user you are logged in with, is an administrator in the OMS portal (under Settings->Accounts->Manage Users).

If the workspace is created from the Azure portal, it might be that the user is not part of this group. To be sure you don`t get this message, you should create the workspace directly from the OMS portal, this way the user is added automatically to the admin group.

Comments (1)
  1. marcus bledsoe says:

    Multiple members of my team have this issue, and we’re all admins. I’ve also tried creating a new OMS workspace in the free tier, and I get the timeouts there as well.

    Any other advice?

Comments are closed.

Skip to main content