cweier
10/19/2025, 11:21 PMArmanda
10/20/2025, 4:44 AMDanni Morgan
10/20/2025, 8:24 AMNuri Ensing
10/20/2025, 8:31 AMLuis
10/20/2025, 2:44 PMRJMNS
10/20/2025, 6:24 PMLuis
10/20/2025, 6:45 PMRondo
10/20/2025, 10:54 PMmescalante
10/20/2025, 11:34 PMKristopher Wood
10/21/2025, 12:52 PMSummer Sun
10/21/2025, 4:55 PMAlex
10/21/2025, 9:22 PMBobby Bukovec
10/21/2025, 10:37 PMPF
10/21/2025, 11:44 PMReece Easton
10/22/2025, 8:59 AMLucas
10/22/2025, 6:51 PMArtur Pacagnan
10/22/2025, 7:42 PMJschmidt
10/23/2025, 10:58 AMAndrii Siryi
10/23/2025, 11:02 AMSim Greenbaum
10/23/2025, 4:19 PMRJMNS
10/23/2025, 6:44 PMDora Sterling
10/23/2025, 8:05 PMKman
10/24/2025, 4:24 AMpen one
10/24/2025, 10:49 AMBetsy Barefoot
10/24/2025, 12:46 PMI'm attempting to update our SAML Azure Federation Metadata XML file to our three environments and am running into an error. To prep for the loading the new XML file, I first deleted the IdP configuration from the three environments by going to Setup > Integration > Manage Authentication > SAML Single Sign-on, clicking Actions, and selecting Delete IdP configuration. I then waited a few minutes before attempting to load the new file.
When I attempt to submit the new XML file in any environment, I get the following error message:
"Identity provider with the entity ID <https://sts.windows.net/d6ac7fd1-6f24-46a4-9996-bfcc1b587137/> is already used by another account and contains different metadata associated with it. Use IDP with a different entity ID or make sure you have the latest metadata file uploaded in all accounts."
It looks like the old IdP data is being retained somewhere. I have double-checked our three environments and confirmed that the IdP settings have been deleted in each.
The XML file needs updating as our Azure SSO certificate was due to expire soon.Rachael
10/24/2025, 8:44 PMJMS
10/26/2025, 4:24 PMcweier
10/27/2025, 7:01 AMShaishav Shah
10/27/2025, 5:34 PMArsen Hacherian
10/27/2025, 6:34 PM