Artisan IMG > Microsoft Calendar (microsoft-calendar) (7afbc06b-9dd6-423c-adb2-6e63f3f8933b)
Microsoft Calendar
Artisan IMG > Microsoft Calendar (microsoft-calendar) (7afbc06b-9dd6-423c-adb2-6e63f3f8933b)

Microsoft Calendar

Microsoft Calendar is the calendar and scheduling component of Outlook


Microsoft Calendar is fully integrated with email, contacts, and other features of your Outlook account. Just as you write in a notebook, you can click any time slot in the Outlook Calendar and start typing.

API Information

The Microsoft Calendar connector has the following Base URL: More information can be found on their main API documentation (v1) site. Details regarding their API limitations can be found here.


Within the builder, click on the Microsoft Calendar connector to display the connector properties panel. Select the 'Authentication' tab and click on the 'New authentication' button.

In the authentication pop-up modal name the authentication in a way that will easily identify it within a potentially large list. For example whether it is a Sandbox or Production auth, etc.

Consider who/ how many people will need access to this authentication when choosing where to create this authentication ('Personal' or 'Organisational').

The second page requires several credentials and check boxes:

Set your 'API version' to 'v2.0'. This refers to the Token URL version that Microsoft Calendar uses.

In order to get the rest of these fields, head to your Microsoft Azure dashboard.

PLEASE NOTE: Microsoft Azure is specifically designed for application management. You must have credentials and access to this dashboard before continuing.

Click on the 'App registrations' option.

Here you will see a list of 'Owned applications'. Select the one you wish to integrate with

Your 'Application (client) ID' is what refers to as your 'Client ID'.

Your 'Directory (tenant) ID' is the 'Tenant ID'.

Copy and paste both the above values into your authentication model.

Your 'Client secret' can be found under the sub-heading 'Certificates & secrets'. This is on the left hand navigation.

Make sure you copy the Client secret VALUE correctly the first time, and save it elsewhere if you think you may need to view it again. If you lose this secret key, you will need to generate/ use a new one.

You need to copy the Client secret VALUE field. As stated above this cannot be revealed twice.

Please create a new client secret if you cannot access the current client secret value.

The 'Https://' credential refers to the pre-configured scopes of the application.

These can be viewed by heading to the left hand navigation once more, and selecting 'API permissions'.

Finally, 'Offline_access' automatically refreshes the authentication token behind the scenes, once it expires.

Once you have added these fields to your authentication pop-up window, click the 'Create authentication' button.

Your connector authentication setup should now be complete.

Available Operations

Please see the Full Operations Reference at the end of this page for details on all available operations for this connector.

Using the Raw HTTP Request ('Universal Operation')

As of version 1.0, you can effectively create your own operations.

This is a very powerful feature which you can put to use when there is an endpoint in Microsoft Calendar which is not used by any of our operations.

To use this you will first of all need to research the endpoint in the Microsoft Calendar API documentation v1.0, to find the exact format that Microsoft Calendar will be expecting the endpoint to be passed in.

Note that you will only need to add the suffix to the endpoint, as the base URL will be automatically set (the base URL is picked up from the value you entered when you created your authentication).

The base URL for Microsoft Calendar is:

For example, say that the 'List calendars' operation did not exist in our Microsoft Calendar connector, and you wanted to use this endpoint. You would use the Microsoft Calendar API docs to find the relevant endpoint - which in this case is a GET request called: /me/calendars.

More details about this endpoint can be found here.

As you can see there is also the option to include a query parameter, should you wish to do so. So if you know what your method, endpoint and details of your query parameters are, you can get a list of calendar information with the following settings:

Method: GET

Endpoint: /me/calendars

Body Type : Raw

Final outcome being: