This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
After creating backup in Microsoft authenticator app, when I am checking details of backup the date of creation and last update date is showing as invalid.
A Microsoft app for iOS and Android devices that enables authentication with two-factor verification, phone sign-in, and code generation
![](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(25.6, 12%, 12%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EB%3C/text%3E%3C/svg%3E)
there are already a few other posts that state the same like https://learn.microsoft.com/en-us/answers/questions/868136/ms-authenticator-backup-was-invalid.html. However up til now no-one from MS seems to have been acknowledging this.
I tried and tested a (by the looks of it) successful recovery unto another device. It shows up all entries and seems to be working. Before I also made a backup of the entries on said other device, which worked and showed an actual date. However when doing the same again on my phone, it showed the same invalid data error.
No idea if that would even work to restore on a phone, but a restore to an android based tablet worked nonetheless, but I don't like this invalid date one bit. Also the fact that it does not generate an error at all in the app itself. For example when you don't have a backup active, this is reflected in the app, but this invalid date doesn't seem to be shown unless you actually look at the backup (that should have been) made.
For me the whole backup possibility was the main reason to choose the MS Auth app to begin with, compared to that of another large cloud provider, which would require to restore all accounts separately...
Thanks @bartoque for sharing that, I also thought to do that, but I was afraid about if backup with invalid dates failed. Anyway, hope to get it fixed in next update, yeah but aesthetically and logically backup looks ugly without dates.
It is working again as before after the June 22nd update of the app. Now actual timestamps are being reported, no longer any "invalid date" message being mentioned.
Haven't tested a recovery on a 2nd device yet with the latest version (which I tried earlier on, which worked, even when the invalid date was reported on my phone, recoveey on a table worked with the previous version).
Really looking forward also to improvements like keeping entries in sync on multiple devices, as that would make life even easier. Also would people have validating things are the same. Might not wanna perform a recivery for recovery's sake, to find out that the backup was no good on your primary device.
I also don't know why a backup is restricted to using a private MS mail address only and not any other selectable cloud account? Or to be able to migrate between android and iphone (using icloud instead of MS mail account) transparently?