Skip to content

Latest commit

 

History

History
71 lines (47 loc) · 3.89 KB

README.md

File metadata and controls

71 lines (47 loc) · 3.89 KB

Event concierge

Follow on Twitter Star on Github Support me on Github Check my blog

Sync your calendar to a different tenant with Power Automate.

Download the solution

Keeping your calendars in sync as a consultant with two or more Office account can be a challenge. This small flow will automatically copy (some) of the event details to your second (or third) calendar, and update/delete those copied if the original event changes or is deleted.

Be sure to check policies to see if you're allowed to do this, you can also limit the details that get copied and only create basic "external event" events in your calendar, so at least your free/busy information is complete for everybody.

Sync Calendar flow

complete flow

flowchart TD
    A[Event added, updated or deleted] --> A1{Event added?};
    A1 -- Yes --> A2{Skip event?};
    A2 -- No --> A3[Create event in destination calendar];
    A3 --> A4[Save ID for copied event];
    A1 -- No --> U1[Lookup Event ID saved earlier];
    U1 --> U2{Event updated?};
    U2 -- Yes --> U3[Update event details];
    U2 -- No --> D1[Delete event from calendar];
    D1 --> D2[Delete row in storage];
Loading

Prerequisites

  • Power Automate license (premium not required)
  • Two Office 365 accounts (you can also change to sync between your calendar and a shared one)
  • Specific excel file in your OneDrive for business

Create Excel file

To correlate the original event and the copy I needed some storage and Excel seems like a viable option.

Download this excel file and place it at the root of your OneDive as /event-concierge.xlsx. If placing it in the root folder isn't an option, you'll need to change the actions with the Excel logo to point to the correct location.

This Excel is nothing special, it has one worksheet with a structured table on it. This table will be used to save both the original event ID and the event ID of the copy, so we can also process updates.

excel table

To not force a premium license for Power Automate to everybody, I wanted to only use "standard" connectors. If the premium license would not be an issue, I would probably use Dataverse for storage

Updates

Follow on Twitter Check my blog

This is my first ever flow build in Power Automate, so be kind! It all started with this tweet.

If you think this flow helped you out, be sure to let me know on twitter and start following me for updates.

You can also follow my blog where I'll be posting more of these awesome flows for Power Automate.