Forum Discussion

JeremyTBradshaw's avatar
JeremyTBradshaw
Iron Contributor
Jan 27, 2021

To Do changes for on-premises mailbox users

Since I don't see this having been announced in the To Do blog or in the Microsoft 365 Message Center, I'm sharing this here. ------------------------------------------------------------ https://su...
data loss
On-Premises
To Do
warning
bart_vermeersch's avatar
bart_vermeersch
Iron Contributor
Jan 29, 2021

We received this in the Message center beginning of this week, together with a list of AAD user GUIDS of impacted users in our tenant.

 

But the message has now disappeared?? :sad:

 

The beginning of the message said:

 

Microsoft is committed to transparency regarding incidents that affect our customers. As part of this commitment, we’re writing to inform you that a recent misconfiguration inadvertently resulted in the unsupported ability of your users to access Microsoft To Do within your on-premises environment, including Tasks within Teams. This access is unsupported for tenants with on-premises accounts and can cause permanent data loss of To Do lists after performing a migration to Exchange Online mailbox. In efforts to prevent any actual data loss and to mitigate the impact we’ve changed access of Microsoft To Do into a read-only state for your organization on Friday, January 22, 2021 that will last until February 22, 2021. After February 22, 2021, your users will no longer have access to Microsoft To Do, or Teams Tasks permanently as this feature was not intended for use in on-premises environments. During that time, you will need to take the steps outlined below to preserve your data.
JeremyTBradshaw's avatar
JeremyTBradshaw
Iron Contributor
Jan 30, 2021
That is interesting to see. The tenant where I saw this issue had at least one user impacted, and there was no message like this. I wonder how they determine who to notify, and if they purposely retracted the notifications as you experienced.

This wreaks of badness.
  • katherinewilkinson2020's avatar
    katherinewilkinson2020
    Copper Contributor
    Feb 01, 2021

    JeremyTBradshaw  Yes it's very fishy. We are now facing the prospective of emailing the whole company as we don't have a list of affected users! Very disappointed in how Microsoft has dealt with this mistake of theirs...

     

    We are in the process of migrating to exchange online, but this is not something we can do overnight!

    • JeremyTBradshaw's avatar
      JeremyTBradshaw
      Iron Contributor
      Feb 01, 2021

      katherinewilkinson2020 You might have good results using Azure AD Sign-Ins to figure out who all was using To Do while their mailbox resided/resides on-premises.  I had a look in Sign-Ins and found that the Application name can show up as either "Microsoft ToDo....." or "Microsoft To-Do....", so you probably want to filter Application for 'Starts with' = 'Microsoft To'.  I was only able to find traces of the desktop app under Non-interactive sign-ins; everything interactive shows as the web client, though my usage of To Do is minimal, so you might see different results in your tenant.

Resources