We are pleased to share that the OHDSI MS Teams environment and collaborator emails are being restored. Most collaborators should have access now, and the remaining accounts will be fully operational shortly.
We know this has been a challenging few weeks, and we sincerely apologize for the disruption. Our team has implemented new security measures to ensure the stability and resilience of our open-science infrastructure moving forward.
๐๐๐๐๐ฌ๐ฌ: Most guest and collaborator accounts are active. If you donโt have access yet, you should by the end of the week.
๐๐๐๐ญ๐ข๐ง๐ ๐ฌ: Regular community and workgroup calls will resume via the OHDSI tenant starting next week.
๐๐ฒ๐ฆ๐ฉ๐จ๐ฌ๐ข๐ฎ๐ฆ: The deadline for plenary and tutorial submissions has been extended to Friday, Feb. 20 (OHDSI2026 โ OHDSI).
To hear the full โpost-mortemโ and learn about our path forward, watch the Feb. 10 community call here: https://youtu.be/naIXwisisx8#JoinTheJourney
No sure if a more detailed error helps, but here it is anyway:
Request Id: b24d8910-445b-4d43-a2ca-36423fa77400
Correlation Id: 9eb4e391-2cc4-4c99-9afe-58ccf9a13105
Timestamp: 2026-02-13T08:31:40Z
Message: AADSTS50020: User account โe.fridgeirsson@erasmusmc.nlโ from identity provider โhttps://sts.windows.net/526638ba-6af3-4b0f-a532-a1a511f4ac80/โ does not exist in tenant โOHDSIโ and cannot access the application โ5e3ce6c0-2b1f-4285-8d4b-75ee78787346โ(Microsoft Teams Web Client) 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.
Hi all, yes, we are now having new technical dificulties with our OHDSI MSTeams environment and email accounts. We are hopeful our colleagues at Microsoft and BTPros can resolve the issue and identify root cause so that we dont experience this more. We will use the forums and ohdsi linkedin to provide updates as we learn more. Sorry all for the inconvenience and thank you for your patience.
๐ผ๐๐
๐๐๐: ๐ฐ๐โ๐ ๐๐๐๐
๐๐ ๐๐ ๐๐๐๐!