Microsoft Graph Permissions for Zimbra to Office 365 Calendar Migration

This application uses Microsoft Graph, and follows its permissions reference so that this application can obtain access without a user

There are THREE STEPS you must follow

1.       Find your Office 365 Tenant ID

2.       Create a new App Registration for the Z2O365 application

3.       Update the appsettings.json file

This is the walk-through:

1.       Find your Office 365 Tenant ID in the Azure AD Portal:

a.       Login to your Microsoft 365 Admin Center or Microsoft Azure as an administrator.

b.       We found the “PREVIEW” version to be a better experience (as of 1/30/2019)

NOTE: if you select preview, you can skip this step -- you will be able to see the tenant id in the second step

c.       In the Microsoft Azure portal, click Azure Active Directory.

d.       Under Manage, click Properties. The tenant ID is shown in the Directory ID box

2.       Create a new App Registration for the Z2O365 application

a.       Login to your Microsoft 365 Admin Center or Microsoft Azure as an administrator. (you just did this above)

b.       In the Microsoft Azure portal, click Azure Active Directory.

c.       Under Manage, click App registrations (preview)

d.       Create a new Registration

                                                   i.      Enter a name (your choice)

                                                 ii.      Select accounts in this organizational directory

                                               iii.      Click Register

                                               iv.      Under View API Permissions, Add permissions calendar read/write, contacts read/write

                                                 v.      Grant Admin Consent

                                               vi.      Under Certificates & Secrets, create a Secret

3.       Update the appsettings.json file

·         Under the AppSettings, add:

o   The APP Name

o   AppTenantID

o   AppID

o   AppClientSecret

Non-mapping contact info in migrations from Zimbra to Office 365

It happens.

You have data in custom contact fields in Zimbra that do not map one-to-one to existing contact fields in Office 365.

So this contact, Horatio Warmonger in Zimbra has info like this:

Note his current "Note:" field in Zimbra pre-migration:

Have no fear -- Sumatra's migration takes all contact data not readily categorize-able in Office 365 and inserts it into the Notes field.

Calendar Recurrence Patterns NOT supported by Microsoft Graph and What Sumatra Does About Them

Microsoft is obsoleting Exchange Web Services (which is too bad since it's been working like a champ) in favor of Microsoft Graph (which is too bad since it's.... immature.)

One of the sad consequences of this is that some recurrence patterns for calendar events which can be created in EWS are impossible to create in Graph.

For example:

What does this have to do with the price of tea in San Francisco?

We're in the business of migrating calendars.

When the recurrence pattern isn't something we can re-create we get testy.

We insert in the standard format, hoping that when Microsoft Graph gets its act together to deliver something like this we're going to be seamlessly running.  Even though the results are a little weird on insert you can correct them by opening the series and re-setting in Outlook.

But we do make it easy to find these.

We tag problem recurrences with "ZimbraRecurrencePatternNotMigrated" (this is configurable on a server-basis).  So you can readily find them.

You can easily sort them all together in Calendar List view:

You can also set the color for these categories to find them in your calendar.

Note that in the above example we have the category "ZimbraMeetingsYouOrganize" (yes, the names are configurable on a per-migration basis) to help you find meetings you organize and re-propose them.  Our full-state migration process makes this step unnecessary.  But full-state is also more expensive.

Migrate Zimbra Calendar and Contacts to Office 365

Since 2001 Sumatra Development has been doing full-state migrations of legacy calendar systems, where meetings are functional meetings and guest lists are functional in meetings.

This is our answer to demands for a less expensive, simpler, faster migration path for smaller sites and enterprises that do not need full-state meetings.

If you can migrate your email from Zimbra to Office, you can now migrate your calendars and contacts, using the same permissions and similar methods.  No limits on the number of users you can migrate but we cap code at 30 days (we're willing to talk on timing).

This is a fast, simple method for moving calendar and contacts from Zimbra to Office 365.

So Jimi Hendrix's calendar in Zimbra:

Becomes his calendar in Office 365 in a few seconds (as opposed to a PST or an export/import).

Since this is faster, simpler, and cheaper, we do not re-create meetings in this version -- but we do make it easy for you to find meetings you organized and the guest list:

Our experience so far shows this method takes considerably less than half the time and effort on the part of Admins than our full-state solution, and that it is of course much faster than client-side solutions.

Win-win!