This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(262.40000000000003, 62%, 35%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ENB%3C/text%3E%3C/svg%3E)
During implementtion of the B2C logout process I used the Chrome browser and it was pretty much trouble free - I used the logout endpoint url as specified in the app registrations section in AAD B2C and added the post_logout_redirect_uri to the end of that, which was my app's home page. I also added the Logout URL to the app in B2C, and added code to clear all sessions and cookies when that url is requested. The whole logout process would end up at the login page, which was the expected behaviour.
I've since tested this in several different browsers, but there are issues with logging out when using IE11 and Edge (currently on v44). When attempting to logout, both browsers would request the logout endpoint, then the Logout URL would be requested, but when redirecting to the post_logout_redirect_uri it would just log me back in.
I managed to resolve the issue with IE11 by changing the post_logout_redirect_uri to another page, which clears all sessions and cookies again and then redirects to the home page. This seems unnecessary, but at least it worked.
Unfortunately the inclusion of the extra step has not solved the problem in Edge; it still logs me back in. It will only log me out once I close the browser.
I have seen several similar posts online about problems with logging out when using Edge, but I have yet to find a definitive answer. Can anyone help please?
I'm reaching within the product team and will come back to you.
@Neil B Does this happen with local accounts? federated accounts? social accounts? all of the above?
if SSO is happening that would certainly indicate some cookies are not being cleared. What cookies remain present after logout and where?
We're only using local accounts. I've managed to get Edge to logout by slightly changing the way the cookies are deleted (I guess Edge is quite fussy??). However, there are still issues with Single Sign Out when using Edge.
We have 3 sites (all ASP.Net Webforms) and if I logout of one of them, it does not log me out of the other 2 sites in Edge - if I refresh the page or click a link in either of the other sites I'm still logged in. But if I do the same using Chrome or Firefox, for example, it logs me out of all sites with no problems.
So I have questions:
Thanks
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(246.4, 47%, 33%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ENB%3C/text%3E%3C/svg%3E)
anonymous user-msft I've just discovered in Edge and IE11 that after I have logged out of any of our sites, if I go back to any page then it logs me back in! All sessions and cookies are definitely being cleared, but it looks like the problem is that it's not actually logging out of B2C, hence why it auto logs me back in when visiting any page.
In Chrome and Firefox the network trace shows the request to my app's Logout URL, but there is no request to it when using Edge. It must also be doing the same in IE11, but I can't check the network trace because the Developer Tools disappears upon clicking the logout link.
Is this a bug within the browsers, or is this a B2C issue? I'd really appreciate a quick response because this is due to go live very shortly, but as things stand that's not going to happen with this problem outstanding.
Thanks
anonymous user-msft Some additional information for you - I added some logging into our logout pages, and I also checked the IIS logs, and I can confirm that when using Edge and IE11 there is never a request sent to our Logout URLs.
Ok I'm forwarding all that information to the product team.
Is there an update available for this issue at all? Thanks
@Neil B due the complexity of the issue please open a support ticket. They will guide you and most possible ask and analyze a fiddler trace. Once you do that please come back and share your support ticket case via a private message so we can keep track of it.