- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-05-2023 12:58 PM
I keep getting an error when navigating to the Employee Portal tab in Microsoft Teams: Error while authorizing the user.
I'm thinking the issue is because I followed the instructions here: https://docs.servicenow.com/bundle/sandiego-employee-service-management/page/product/sn-teams/task/d... as a single-tenant setup. It says, "For single tenant, you must provide the Application (client) ID and Directory (tenant) ID in the Configure Tab section."
However, the Application and Directory ID fields will not display for me. I am thinking this is why the portal won't show? Any idea what is going on?
One other thing I read which may be a problem is I am using a different email address to access our test environment in Teams than my main work one that I use to access our ServiceNow environment. Maybe that's the issue? Then again I don't know why those two ID fields will not show.
Thanks,
Jesse
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-05-2023 02:03 PM - edited 01-05-2023 02:06 PM
My fault. The way documentation is organized (frustrating) there's no warning that you have to modify a system property to point to /esc even though that's the default employee portal and the embedded OOB-looking portal in Teams that initially displayed has a link to the correct portal (circled in my previous post/screenshot).
https://docs.servicenow.com/bundle/sandiego-employee-service-management/page/product/sn-teams/task/c...
We now have the correct portal displaying after stumbling across the page linked above. Still not sure why the Config tab for the manifest is missing those ID fields if they are required for single-tenant.
Thanks.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-05-2023 01:45 PM - edited 01-06-2023 07:42 AM
Ok we kind of got it working after updating our emails to use our development ones vs production (wish that info was in the documentation and not a random blog post I found). However, an OOB-looking portal is displayed with a link to our correct portal. Why does the portal in Teams look different than the one we created?
What it looks like in teams:
click the link I circled in the image takes you to the correct portal. Why isn't it displaying like this?
I had our O365 admin try and he gets a bunch of errors in teams under the portal tab. Maybe because it's displaying the wrong portal?
Any thoughts?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-05-2023 02:03 PM - edited 01-05-2023 02:06 PM
My fault. The way documentation is organized (frustrating) there's no warning that you have to modify a system property to point to /esc even though that's the default employee portal and the embedded OOB-looking portal in Teams that initially displayed has a link to the correct portal (circled in my previous post/screenshot).
https://docs.servicenow.com/bundle/sandiego-employee-service-management/page/product/sn-teams/task/c...
We now have the correct portal displaying after stumbling across the page linked above. Still not sure why the Config tab for the manifest is missing those ID fields if they are required for single-tenant.
Thanks.