microsoft authenticator new phone without old phone

We recommend not using the password created by your mobile and instead create one that you can remember in case you log in with another device.

Click the ‘Forgot my password’ link after entering your User ID when logging in or go directly to the SSPR tool and follow the prompts.Ī strong password requires 8 to 256 characters and must combine uppercase and lowercase letters, numbers and symbols.

Seems that something prevents IE from caching that page and thus back button returns some very old cached version.You need your User ID and your usual MFA device handy to complete these steps via the Microsoft Self-Service Password Reset (SSPR) tool: SMS authentication users

When the user first navigates to our site, they see the fresh version of the page.

That's totally ok for me, but NOT ok if the cached page is a week old.

According to this blog post from MS ( ) pressing the back button should not retrieve the page from server, even if the cached page is not fresh.

Some users have said that this issue happens on other sites as well.

There are no other cache related directives in response headers or in HTML meta tags.

Disabling browser caching is not an option.

The server response contains header Cache-Control:max-age=60.

Has anyone else seen this bug bug in Mobile Internet Explorer 9? How could I prevent this from happening?

User sees a very old (a week or so) version of the frontpage.

User clicks a link to an article and navigates to the article pageĪfter clicking the back button, user sees the frontpage, exactly the content what she saw before navigating to the article page.

User navigates to the news site frontpage and sees a fresh and up-to-date version of the page.

Number of users have reported this bug in Windows Phone 7.5 IE 9.0 Mobile: I'm building a news website with dynamic content that updates frequently (many times per day).

Microsoft authenticator new phone without old phone