Customers who have multiple SuccessFactors instances, and also multiple Teams Azure Tenants, you are unsure how the mapping of the two works and are wondering how to test out our Microsoft Teams Integration features in Preview and Production, then read on!
Testing Practice for Custom App (from 1H 2023)
As you may be aware, as of 1H 2023, we delivered our App through a ZIP file in Admin Centre. Which means, you need to upload the custom App through a zip file Teams Admin Centre.
The general rule is, on one DC/env, the mapping of SuccessFactors company and Azure Tenant need to be 1:1. You should always have dedicated SuccessFactors preview instances map to a dedicated Teams Tenant preview instance, the same goes for Production. Here is an example:
SuccessFactors Company ID
Azure Tenant ID
Set up your connection in Work Tech Configuration page. Make sure you connect to TeamsTenant1.
Our Teams integration will only work when Production hits, there is no concept of a Preview release for Teams integration. Therefore if you need to test the feature, the environment you use for testing can be both Preview, but the time of testing has to be when we hit Production.
Set up your connection in Work Tech Configuration page. Make sure you connect to TeamsTenant2.
Table 1: an example of how a best practice mapping relationship should work
Testing Practice for App Store App(from 2H 2023)
You may have seen this item in the Roadmap Explorer that we have plans to release our App in the Teams App Store, making this App more public and global, we like to call this our newest and Latest App.
What this means is that you are no longer required to upload a zip file of our App to make it available for your users, because admins can now see our new Latest App in the App Store and allow download for all your end users. As a result, this will make our previous App a Legacy App, which you now need to migrate to the new App if you have already installed the Legacy App.
What this means for new customers in 2H 2023:
if you are a new customer from 2H 2023 and want to enable the SuccessFactors App, you will be able to search for it in the Teams App Store and install it, this is where you can choose to 'allow download' for your end users. No problem there!
What this means for existing customers in 2H 2023:
if you are an existing customer who have already installed the Legacy App (via zip file) before 2H 2023, you will be subjected to a Legacy App to Latest App migration. In the same Teams environment, you cannot use Legacy App and Latest App (connected to the same SuccessFactors instance) at the same time as the notifications/messages will have no single endpoint to go to. Here is what you need to do:
Test our the Latest App by downloading it from the Teams App Store in your Preview Teams environment and a Preview SuccessFactors environment. It is always recommended to test the App first in your Preview Teams tenant. (This App will only be available when Production hits, there is no concept of a Preview release for Teams integration. Therefore if you need to test the feature, the environment you use for testing can be both Preview, but the time of testing has to be when we hit Production)
After you download this new App, don't forget to establish consent and connection in the corresponding Work Tech Configuration page. Refer to Table 1 above on which environments you should use.
Once you are happy with the features in Latest App, you are now ready to enable the App for your Production SuccessFactors environment and Production Teams environment. Go to your SuccessFactors Work Tech Configuration page and disconnect from the previous Legacy App. Once you disconnect, there's no going back, you cannot re-connect to a Legacy App anymore.
Re-connect the same SuccessFactors environment to the same Teams Environment that you have been using in the Latest App section of the Work Tech Configuration page.
Deprecation plan of Legacy App
Legacy App will coexist with the new Latest App for around 3 months after 2H 2023 release, timelines subject to change. Please use this opportunity to ask questions about the potential migration questions you may have. After deprecation, Legacy App features will not work anymore.