Hi,
After deploying Microsoft Teams integration-related Update Sets to our QAS instance, the integration stopped recognizing logged-in users correctly. Now, every user is treated as a guest, whereas on DEV, everything works fine.
Additional details:
- All Teams-related notifications work correctly, but user recognition fails.
- All users are affected, not just specific ones.
- No changes were made in Azure AD related to this integration.
- User emails in ServiceNow match those in Azure AD.
- There were no significant configuration differences between DEV and QAS before the issue appeared.
- This happened immediately after the Update Set deployment.
Troubleshooting attempted:
- We verified that the Update Sets were moved correctly.
- We compared configurations between DEV and QAS but found no clear differences.
- Notifications in Teams are still working, but user identification is not.
Questions:
- Has anyone encountered a similar issue where users are suddenly recognized as guests after an Update Set deployment?
- Would backing out all Teams-related Update Sets from QAS and redeploying them as a batch be a reasonable approach?
- Are there specific settings we should verify regarding user profile linking between Azure AD and ServiceNow in Teams integration?
Any insights or suggestions would be greatly appreciated.
Thanks in advance!
