...
| Code Block | ||
|---|---|---|
| ||
Request Id: 12345678-2e3b-4c96-8e98-e10e6ec52400 Correlation Id: 12345678-0f20-4d51-9012-13e6313806a8 Timestamp: 2022-10-17T09:26:02Z Message: AADSTS90072: User account 'test.person@testorg.org' from identity provider 'https://sts.windows.net/12345678-abcd-1234-a1b2-123456789abc/' does not exist in tenant 'WMDA Services' and cannot access the application '18373cfc-5469-463f-8793-bd3d30fb9a9b'(WMDA - Search+Match SPA Prod) in that tenant. The account needs to be added as an external user in the tenant first. Sign out and sign in again with a different Azure Active Directory user account |
Issue & solution:
You are logged in with your organisation's Microsoft account (in this case test.person@testorg.org) in the same browser as the one you are using for logging into Search & Match or other WMDA services. You are probably using it for services such as Office365/Microsoft365 which include outlook. In order to prevent these issues please use a browser that is not logged into your organisation's office365/microsoft365 account. You can also use incognito/inprivate mode for that.
If the issue persists, there is an alternative way of logging in ("B2B"). It involves using your own organisation's Microsoft account (in this case test.person@testorg.org) to login to the WMDA Portal, Search & Match and future other services. Instead of having a separate password for WMDA services, you keep using the password from your own organisation. Your own Microsoft account is "invited" into our environment as a guest. There is just another layer of MFA that is enforced on the WMDA side in order to help secure the applications.
...
Now you can set up MFA in the same way as described in the MFA user guide.
Updated login procedure
After you have accepted the invite and have successfully setup MFA, you are now able to login. The following is different compared to logging in using the normal method:
WMDA portal
Search & Match Service
