Teams Troubleshooting

Use this page when private organization work does not behave as expected.

A User Cannot Access The Organization

Check:

Did they sign in with the right email?
Were they invited or added?
Did they finish sign-up?
Does the organization require SSO?
Are they opening the Teams app, not Customer or Spaces?

If SSO is involved, the identity provider owner may need to help.

A Booking Cannot Be Created

Common reasons:

the resource is unavailable
the location is not set up correctly
the user or team is not selected
the time is invalid
the booking conflicts with another booking
the user does not have access

Open the resource and location pages before retrying.

A Location Is Missing

Check:

organization context
whether the location was created in Teams or Spaces
user access
whether the location is active
whether you are using the correct route or app

Private locations belong in Teams. Marketplace locations belong in Spaces.

A Resource Is Missing

Check:

the correct location
resource setup
availability
whether the resource is connected to the location
whether the user can access it

Microsoft Teams Shows The Wrong Page

Check:

signed-in Microsoft Teams account
Skedular account
organization context
whether the route is a Teams route or Spaces route

If the wrong organization opens repeatedly, disconnect and reconnect through the approved install flow.

Slack Did Not Connect

Check:

Slack workspace permissions
whether the right admin started the install
whether the success page appeared
whether browser pop-ups or redirects were blocked

Analytics Look Wrong

Check:

date range
organization
location filters
resource filters
whether enough booking data exists
whether the metric definition has been reviewed

What To Send An Admin

Send:

organization name
page you were using
booking, location, resource, team, or user name
time of the issue
what you expected
what happened

Do not send passwords, SSO tokens, private member exports, or unrelated personal data.

Actions reference Support handoff