Before going on, please check if there is an already available KBA under category "Collaboration and Work Tech LOD-SF-EAS-WRK " that can help answer your concern. A few examples include:
If you do not find the answers, please read on or post a comment in this blog.
Q: Users are getting an error in the Teams App " The app is unavailable due to user mapping issues. Please contact your administrator for help", what does this mean?
A:The error only shows up under Application type permission. The user in Teams is not uniquely mapped correctly to a user in SuccessFactors, e.g:
- the same email/ID is found for two users in SuccessFactors
- the same email/ID cannot identify any users in SuccessFactors
- the end user must have the permissions (this is documented here)
- Users have the User Permissions > General User Permission > User Search permission and are included in the target population. The Exclude granted users from having the same access to themselves option must not be selected. The defaultLocale field must be configured in the user API.
- Users must not have the Administrator Permissions > Manage User > Employee Export permission. If users have this permission, they must be included in the target population, and the Exclude granted users from having the same access to themselves option must not be selected.
This message will be enhanced in 2025 to reflect possible reasons for failure.
Q: Users are getting an error in the Teams App "Unable to reach app", what does this mean?
A: This is intended to be a generic message as the root cause cannot be differentiated and reflected in the message without troubleshooting, we display this generic message in the hopes of the user trying to access the app again, or asking for admins for help and eventually submit a Support ticket for engineers to take a closer look
Q: Users see error in the Teams App: "Service connection between SAP SuccessFactors and Microsoft 365 hasn't been established". What does this mean?
A: The user has downloaded the App prematurely, before the SuccessFactors Admin or Teams Admin has set up connection in the Work Tech Configuration Page. There are likely missing steps in the Work Tech or Azure configuration, such as user mapping or permissions.
Q: Can I connect one SuccessFactors instance to multiple Teams tenants? What about the other way around? And what happens if I did set up the connection from multiple SF linking to the same Teams Tenant in the Admin Centre?
A: As of 1H 2025, we will support one SuccessFactors instance connecting to multiple Teams tenants. But not the other way around (i.e one Teams connecting to multiple SuccessFactors instances). If you did set up the connection from multiple SF linking to the same Teams Tenant in the Admin Centre, the Teams App won't work properly. At any given time, the request from Teams app will be sent to a connected instance randomly. We do not recommend linking multiple instances for any system.
Q: What aspect of the App appearance can be customized?
The App's name and icon can be customized through Teams Admin Centre. Please see the Microsoft documentation on how to customize those.
Description customization will come end of 2024.
