Office 365 Outlook

This connector is available in the following products and regions:

Service	Class	Regions
Copilot Studio	Standard	All Power Automate regions
Logic Apps	Standard	All Logic Apps regions
Power Apps	Standard	All Power Apps regions
Power Automate	Standard	All Power Automate regions

Contact
Name	Office 365 Users
URL	https://learn.microsoft.com/en-us/connectors/office365users/
Email	idcknowledgeeco@microsoft.com

Connector Metadata
Publisher	Microsoft
Website	https://www.office.com/
Privacy policy	https://privacy.microsoft.com/
Categories	AI;Business Intelligence

To learn how to use this connector in Power Apps, go to Connect to Office 365 Outlook from Power Apps. Some of operations operate with Graph API. You can find Graph API IP addresses in Office 365 URLs and IP address ranges.

Deprecated operations decommission

Due to underlying APIs decommission process, it's highly recommended to update existing solutions to avoid usage of operations marked as [DEPRECATED].

Known issues and limitations with actions

Short description	Operations	Long description
Incorrect email attachment with digitally signed emails	All	For digitally signed emails, the action output may contain incorrect attachment content, which can't be used as input in subsequent actions (for example, to create a new file with attachment content).
Support of HTML/action cards in different mail clients	Send approval email Send email with options	When sending emails with options or approvals, the action card (actionable message) rendering in Outlook won't support HTML in the body of the message (if HTML buttons are clicked, the output of the action can have null values for some fields). The rendering behavior of HTML in the body of the message depends on the options Use Only HTML Message and Hide HTML Message. If Use Only HTML Message is set to Yes, all mail clients will show only the HTML buttons. The action card buttons will not be rendered. If Use Only HTML Message is set to No, and Hide HTML Message is set to Yes, only the action card buttons will show. If Use Only HTML Message is set to No, and Hide HTML Message is set to No, some mail clients will show both the action card and the HTML message, and some mail clients will show only the action card. Actionable Messages are only supported with single user mailboxes. Group and shared mailboxes are not supported. For information on the support of action cards in different mail clients, go to Outlook version requirements for actionable messages.
Receive meeting updates	Update Event (V4)	If you use this operation and you're the organizer of the event, all the attendees will receive meeting updates. Also, due to the current design, all event fields omitted during the update will be reset to default values. Therefore, you need to fill all the event properties with intended values or re-fill current values (please use Get event (V3) action), in case you are not going to update them.
When the event is updated, only one day of the week remains	Update Event (V4)	If the event that you are updating repeats several times a week every week, do not forget to specify these days in the Selected days of week parameter. Otherwise, after the update, one day of the week will be saved, which will be taken from the 'Start Time' parameter.
Set third-party mail filters	Send email with options Send approval email	Third-party mail filters (like G Suite and Mimecast) will autoselect the user options in action. For this reason, set Show HTML confirmation dialog to Yes to avoid this problem related to the functionality.
Send action cards/HTML	Send email with options Send approval email	These actions send action cards (actionable messages) and HTML content. The response will be localized only in case you push the button in an actionable message itself (not in HTML content). In Sovereign clouds, action cards are rendered only to the sender of the email, but not to other recipients. This happens even if the HTML content is rendered for all recipients.
Send an email from a shared mailbox	Send an email from a shared mailbox (V2)	The operation is expected to work for the Microsoft 365 shared mailbox feature only.
Workaround for rooms returned over 100	Get rooms (V2)	The number of rooms returned is limited to 100. As a workaround, query for room lists using Get rooms in room list (V2). Then, search for the rooms inside the selected list.
Email encryption limitation	Reply to email (V3)	Emails that are encrypted aren't supported by the connector when using this action. Therefore, if you try to send an email to Outlook that has email encryption turned on, you'll see the error with a note that the request has failed.
Reply to email action changes datetime to UTC	Reply to email (V3)	Sent datetime of the original email is converted to UTC time zone due to underlying system limitations.
Send an email (V2) does not return message id	Send an email (V2)	There is no way to get the messageid when sending a message.
Send an email from the converted from a personal shared mailbox	Send an email from a shared mailbox (V2)	Action does not work for shared mailboxes that were converted from personal mailboxes.
Maximum number of events returned limitation	Get calendar view of events (V3)	The maximum number of events which can be returned is 256. To retrieve more than 256 events utilize the Skip Count and Top Count parameters to retrieve lists of events in incremental fashion.
Send approval email response returns null	Send approval email	When users click the Actionable Message card options at the top of an email, values for userid, useremailaddress, and usertenantid are retrieved. If users click an option from the email body, these values remain empty. Additionally, when sending an approval email, the response for userid, useremailaddress, and usertenantid is null. In some scenarios, the values for userid, useremailaddress, and usertenantid fields return as null or empty even when the recipient interacts with the native Actionable Message buttons.
Not all calendars are available for users when creating flows	Get calendar view of events (V3)	While using Classic Outlook, users are unable to see all of the calenders created by the creating flow. It is necessary to turn on shared calendar improvements: How to enable and disable the Outlook calendar sharing updates - Microsoft Support. Afterwards, remove and re-add the existing invites.

Known issues and limitations with triggers

Short description	Operations	Long description
Incorrect email attachment with digitally signed emails	All	For digitally signed emails, the trigger output may contain incorrect attachment content, which can't be used as input in subsequent actions (for example, to create a new file with attachment content).
Emails are missed due to system limitations	All	If there are many emails sent at the same time, some emails could be missed by the trigger due to underlying system limitations. This issue occurs rarely and is related to the mail triggers.
Trigger may run twice on emails with attachments with Dynamic Delivery	All	If Safe Attachments in Microsoft Defender for Office 365 is configured with Dynamic Delivery option, the trigger may run twice on receiving a new email. The first time it runs, attachments array in the trigger response is empty. As a workaround for emails with attachments, have a condition after the trigger that verifies whether the length of the attachments array is greater than 0.
Monitor multiple mailboxes or calendars	All	If you want to configure a trigger to monitor multiple mailboxes or calendars, create a separate flow/LogicApp for each mailbox or calendar.
Trigger fires twice	When a new event is created (V3)	When you accept a meeting invitation, the trigger would fire second time for this meeting event. The reason that the Outlook service treats an event after acceptance as a new event and rewrites its Id and created date—it recreates event. The user can work around this issue by filtering the trigger's outputs on the Response type parameter using built-in control module and its action's condition.
Trigger fires for all events in a recurring event	When an event is added, updated or deleted (V3)	Trigger fires on each event occurrence. When you change a recurring event, it affects all events in this series. For example, if a series has 15 occurrences, the trigger will fire 15 times.
Trigger fires with Deleted value in Action Type parameter for events outside interval window	When an event is added, updated or deleted (V3)	When a flow is configured to trigger for events inside of a specific time interval, all events outside of the defined interval — create, update, or deleted — will trigger the flow as Action Type parameter with a Deleted value. This situation can occur because of the following reason: Interval periods are set at the time of the trigger creation and then updated one time per week, i.e., if 6 days have passed since the trigger was created, and the days 30 (before) and 30 (after) were set in the fields, then these dates will be relevant at the time of trigger creation. After 6 days it will look as if 36 (before) and 24 (after) were set. After 7 days, the trigger will automatically update and the dates will again be 30 (before) and 30 (after). The main reason of this limitation is because of Microsoft Graph’s delta query behavior. For more information, go to event: delta - Microsoft Graph v1.0 - Microsoft Learn.
Trigger provides unnecessary updates	When an event is added, updated or deleted (V3)	An event can be updated due to internal Exchange processes and the trigger will fire again because of that. Users can filter a trigger's outputs on the Action Type parameter to ignore unnecessary updates.
Delay in a trigger fire	When a new email arrives (V3) When a new email mentioning me arrives (V3) When an email is flagged (V3) When an event is added, updated or deleted (V3)	Triggers fire on the corresponding event's occurrence almost immediately in most cases, but there could be rare circumstances when the trigger's delay to fire may take up to one hour.
Trigger behavior when an email folder is changed	When a new email arrives (V3) When a new email arrives in a shared mailbox (V2) When a new email mentioning me arrives (V2)	1. Triggers are based on the date and time an email was received. Moving an email to another folder does not change the received date property value, so the triggers will skip any email that was received prior to the latest successful run. For Example : When two emails (A and B) are received in quick succession, moving email B to a folder first sets the trigger time to the time email B was moved. As a result, when email A is moved to the same folder afterward, it doesn’t trigger the action because the trigger is now only looking for emails received after the time email B and moved to folder. 2. Trigger will only check for emails inside folder for which trigger is configured to in flow. If any rules are set to move emails to folder/sub folder, trigger is not expected to fire if trigger is confgured to check emails inside Inbox folder. Please select right folder.
Flow intermittently triggers for older emails when moved to folder	When a new email arrives in a shared mailbox (V2)	The flow intermittently triggers for both older emails and the latest emails moved to another folder. This is by design and may result in inconsistent behavior.
Trigger behavior on flagged email	When an email is flagged When an email is flagged (V2) When an email is flagged (V3) When an email is flagged (V4)	Triggers fire on flagging an email or receiving a flagged email. Also, if an already flagged email is modified in any way (for example, an email category is changed or an email is replied), the trigger will fire on this email. Furthermore, when multiple emails are flagged at once, it causes the trigger to run multiple times for few emails.
Trigger limitation for shared mailboxes	When a new email arrives in a shared mailbox (V2)	The trigger won't work in cases of user-to-user shared mailboxes unless one of the users has full access to the other mailbox (which includes more permissions than just sending emails).
Trigger timeout with attachments	When a new email arrives (V3)	Setting Include Attachments to Yes causes the connector to wait for all attachments to be downloaded. When many emails with attachments arrive around the same time, the connector can timeout while downloading these attachments. To avoid this, the trigger should be changed to set Include Attachments to No, and the logic should be changed to add the Get Attachment (V2) action to download the attachment. Additionally, LogicApps authors should ensure that the Office 365 mailbox and the LogicApp are hosted in the same region to reduce attachment download time.
Trigger limitation when using To Or CC filter	When a new email arrives (V3)	When filtering by the To or CC field, only that field should be populated and the others left empty. If both the To and CC fields are set, then the trigger will fire only for emails that have the emailId(s) in both of the fields.
Email encryption limitation	When a new email arrives (V3) When a new email arrives in a shared mailbox (V2)	The output of triggers does not contain actual message body but will have note mentioning the message is secured and prohibited and this response is from backend.

Common errors

Error	Solution
Access to OData is disabled or most errors when using the connector	Check that the REST API is enabled. Accounts on a dedicated (on-premise) mail server or accounts that are sandbox (test) accounts may also see an error. Your administrator can learn how to migrate a mailbox in How to migrate mailbox data by using the Exchange Admin Center in Office 365. If you are using an EWS application access policy, ensure that the following user-agents are allowed: "LogicAppsDesigner/","azure-logic-apps/","PowerApps/", "Mozilla/", "Microsoft Flow*", "Azure.Connectors.Office365Outlook.Office365OutlookConnector", "Azure.Connectors.Outlook.OutlookConnector", "PowerAutomateLocal/*", "PowerAutomateCloud/*".
REST API is not yet supported for this mailbox	The error can occur if the mailbox is on a dedicated Microsoft Exchange Server and is not a valid Office 365 mailbox. For more details, go to REST API is not yet supported for this mailbox error for request to a mailbox.
Specified object was not found in the store	Verify the permissions for the account. Verify the user account used for the trigger is a member of the shared mailbox. Verify that the original mailbox address field contains the shared mailbox address. Re-check the shared mailbox configuration in the admin center. Delete the current Outlook connection and create a new one. Also, this error is displayed when the message has been moved or deleted by the mailbox owner. To learn more, go to Configure shared mailbox settings.
AADSTS53003: Access has been blocked by Conditional Access policies and the access policy does not allow token issuance and other Conditional Access errors	Conditional Access policies can prevent the connector from running as expected. To learn more, go to the Microsoft Entra ID Conditional Access documentation.

General known issues and limitations

• To use this integration, you'll need access to an Office 365 mailbox that has the REST API enabled. To make a connection, select Sign In. You'll be prompted to provide your Office 365 account. Then, follow the instructions to create a connection.

• There are two types of email attachments:

  • File attachments: Any file, such as a .txt, .jpg, .zip, .pdf, and others. One of the few properties in a file attachment is the base64 encoded content of the file. The latest versions of all triggers support these attachments. EML, MSG, and ICS files should be attached within .zip archives to be available in trigger responses.

  • Item attachments: Email messages, calendar items, and NDR (Non-Delivery Report) emails that are attached to an email. Item attachments have many properties. These attachments, including NDR emails, are not supported by the connector at the moment. To workaround this issue, you can do the following:

    • Use Invoke an HTTP request action under the HTTP with Microsoft Entra ID connector.
    • When creating a connection for the HTTP with Microsoft Entra ID connector, input text https://graph.microsoft.com/ for both Microsoft Entra ID Resource URI and Base Resource URL connection parameters.

    Warning

    Don't use the public endpoint (https://graph.microsoft.com) for national clouds. To learn more, go to Microsoft Graph and Graph Explorer service root endpoints.

    • After connection with HTTP with Microsoft Entra ID is created, use that action with with this Get attachments endpoint.

• We have a size limit of 1MB per data uri for inline embedded images, i.e. the image cannot be more than 1MB after base64 encoding. This only applies to embedded images inside of the mail body. Bear in mind the size of an image after being converted to a base64 string increases. Depending on the image compression, format, and other characteristics it can increase anywhere between 25% to 50%. For instance, an image of more than 700KB will after being converted to a base 64 string likely exceed the 1MB limit stated above.

• An Office 365 group address can't be used as shared mailbox address.

• If the email is sent outside of the associated organization, the admin should check if the organization has specific rules to reject sending/forwarding emails outside of the associated organization (for example, using SMTP headers). To learn more, go to SMTP headers.

• Shared calendars are listed in dropdown of calendar ID in any calendar related trigger/action only if user has view and edit to them. Please make use of Get calendars (V2) action to get list of calendars and its access. More Info on sharing calendars and setting permissions visit Share an Outlook calendar

• Forward slash symbol / isn't supported for folder names in case of custom input value for Folder parameter. As a workaround, use file picker, or provide folder Id value.

• In some rare cases, newly created users get a connection error despite required permissions granted to their accounts. The workaround would be to switch/re-authenticate the shared mailbox connection with the email address and password of the shared mailbox account. This way, the flow should run successfully for all users.

• After the permissions are granted for the account to access the shared mailbox, it can take about two hours until the permissions are replicated on the platform.

• Each email will count as only one API call per connection, even if there's more than one recipient in the To, Cc, or Bcc fields. To learn more about sending limits, go to sending limits.

• In some circumstances, non-Latin characters won't render as expected when sending an email with an adaptive card inside it. To learn more, go to Known issues with HTML to PDF conversion. As a potential workaround, use the same type of characters in the email subject as used in adaptive card.

• Sending email with Adaptive Cards are only rendered for owner of the flow due to Backend Limitation. Adaptive card supported scenarios.
  When sending actionable messages to anyone else, the "originator" property must be set to a valid provider ID generated by the Actionable Email Developer Dashboard

• Currently, Office 365 does not support Service Principal-based authentication.

• For calendar related events involving shared experiences, please note that each user has a unique calendar ID. You can confirm this by using "Get Calendars(V2)" for both the owner and the shared user, as these IDs are provided by the backend graph service. As a result, when using a shared user connection, the flow may encounter a ** 404 - "ErrorItemNotFound"** error.

  • As a workaround, if you are sharing the flow with another user as a co-owner, ensure that the owner’s connection is used when running the flow. Alternatively, you can share the flow as a RUN ONLY user to utilize the owner’s connection instead of the Run only user’s connection.

• In some cases when using Send an email V2 to send multiple attachments, the resulting files may be invalid. In those cases it is best to follow the below process as a workaround.

  Save multiple attachments to an email as an array of attachments:

  

  1. Initialize a variable of type array
     
  2. Use the Append to array variable action to add each attachment to the array
     
  3. Set the attachment variable using a dynamic expression referencing the array
     

Throttling limits on the Office side

In addition to the throttling limits per connection, Office imposes its own limits per inbox. This limit can be reached if the user creates different flows/Logic Apps that target the same inbox. To learn more, go to the Exchange Online limits documentation.

Connector timeouts detail

Office 365 Outlook connector makes outgoing requests to one of the following APIs:

• Graph API, which has 30 seconds timeout interval per single external request.
• Outlook REST API, which has 60 seconds timeout interval per single external request.

This error will be returned after a request to these external APIs reached the limit: { "status": 504, "message": "Request failed. Try again later"} Such failed requests will be retried up to four times in Power Automate/Azure Logic Apps (unless the default retry policy is overridden by the user). To learn more about retry policy, go to Handle errors and exceptions in Azure Logic Apps.

The 504 (gateway timeout) status code returned doesn't imply the underlying action was unsuccessful. Due to default retry policy (if applied), the same action can be executed multiple times. For example, if the Send an email action results in a 504 response, and it retries the request, then duplicate emails are possible.

Deprecation of Webhook trigger

Due to a recent change in the lifecycle of webhook subscriptions, the When a new email arrives (webhook) trigger has been deprecated. While we are working to provide a solution to this, use the When a new email arrives polling trigger instead.

Shared mailbox support

As of May 6, 2020, shared mailbox support was added for certain operations with an optional Mailbox address parameter, which allows you to specify a shared mailbox address for your operation to access. If you were using this operation prior to May 6, 2020, you'll need to explicitly update your operations to specify the shared mailbox address.

For operations that don't support shared mailboxes yet, you can use a workaround with the Invoke an HTTP request action under the HTTP with Microsoft Entra ID connector. When creating a connection for the HTTP with Microsoft Entra ID connector, input text https://graph.microsoft.com/ for both Microsoft Entra ID Resource URI and Base Resource URL connection parameters. After it's created, you can go to Outlook mail REST API to set the URL, and optionally the request body to call its shared mailbox APIs. Some of the Outlook functions will only be available on the beta version of Graph API. The HTTP with Microsoft Entra ID connector is a premium connector and won't be available if you are using the free version of Microsoft Power Automate.

Add hyperlinks to the email body

For adding hyperlinks to the email body, you can do the following:

• In the Body field, mark the text you want to link, and then select the Link icon.
• When you see the dialog, paste your link address into the Link Target field, and then select the Add button.
• To verify that everything is correct, place the cursor over your new link. When you see the small icon, select it to open the linked page.

SMTP headers

The connector is attaching the following SMTP headers (Internet message headers) to each sent email:

1. "x-ms-mail-application" with the following values:

   Service	Value
   Power Automate	Microsoft Power Automate; User-Agent: azure-logic-apps/1.0 (workflow <workflow id>; version <version id>) microsoft-flow/1.0
   Power Apps	Microsoft Power Apps; User-Agent: PowerApps/<version id> (<Player type>; AppName=<app name>)
   Logic Apps	Azure Logic Apps; User-Agent: azure-logic-apps/1.0 (workflow <workflow id>; version <version id>)

2. "x-ms-mail-operation-type" with the following values:

   Description	Value
   For reply email operations	Reply
   For forward email operations	Forward
   For send email operations (including SendEmailWithOptions and SendApprovalEmail)	Send

3. "x-ms-mail-environment-id" with Environment Id value.
   The presence of this header depends on the product you are using:

   • In Power Apps, it will always be present.
   • In Power Automate, it will only be present in newly created connections.
   • In Logic Apps, it will never be present.

4. "x-ms-mail-workflow" with the following values:

   Service	Value
   Power Automate	x-ms-workflow-name: <workflow name>; x-ms-workflow-run-id: <workflow run id>; x-ms-client-request-id: <client request id>;
   Logic Apps	x-ms-workflow-name: <workflow name>; x-ms-workflow-run-id: <workflow run id>; x-ms-client-request-id: <client request id>;
   Power Apps	x-ms-client-request-id: <client request id>;

Working with attachments

Certain triggers and actions have a parameter to control whenever attachments content should be included into the response - Include Attachments. This parameter controls only attachments content, but not the attachments metadata (like Id, Name, Content Type, Size, and Is Inline), which would be included in the response regardless of the parameter value.

Connector in-depth

To learn more about the connector, go to Connect to Office 365 Outlook using Azure Logic Apps.

General Limits

Name	Value
Maximum mails content length (in MB)	49
Maximum total mails content length per connection per 5 minutes for 'Send an email' actions (in MB)	500
Maximum total content length per connection per 5 minutes for ALL actions (in MB)	2000
Maximum number of options for options and approval mails	100
Maximum number of megabytes being transferred from the connector concurrently	300
Maximum number of requests being processed by the connector concurrently	70

Creating a connection

The connector supports the following authentication types:

Office 365 Credentials (Office GCC High)	Log in with Office 365 Credentials (Office GCC High).	Azure Government only	Not shareable
Office 365 Credentials (Office Public/Office GCC)	Log in with Office 365 Credentials (Office Public/Office GCC).	Azure Government only	Not shareable
Default	Log in with Office 365 Credentials	All regions except Azure Government	Not shareable

Office 365 Credentials (Office GCC High)

Auth ID: oauthGccHigh

Applicable: Azure Government only

Log in with Office 365 Credentials (Office GCC High).

This is not shareable connection. If the power app is shared with another user, another user will be prompted to create new connection explicitly.

Office 365 Credentials (Office Public/Office GCC)

Auth ID: oauthPublic

Applicable: Azure Government only

Log in with Office 365 Credentials (Office Public/Office GCC).

This is not shareable connection. If the power app is shared with another user, another user will be prompted to create new connection explicitly.

Default

Applicable: All regions except Azure Government

Log in with Office 365 Credentials

This is not shareable connection. If the power app is shared with another user, another user will be prompted to create new connection explicitly.

Throttling Limits

Name	Calls	Renewal Period
API calls per connection	300	60 seconds

Actions

Assign a category to multiple emails	This operation assigns an Outlook category to multiple emails.
Assigns an Outlook category	This operation assigns an Outlook category to an email.
Create contact (V2)	This operation creates a new contact in a contacts folder.
Create contact [DEPRECATED]	This action has been deprecated. Please use Create contact (V2) instead. This operation creates a new contact in a contacts folder.
Create event (V1) [DEPRECATED]	This action has been deprecated. Please use Create event (V4) instead. This operation creates a new event in a calendar. (V1)
Create event (V2) [DEPRECATED]	This action has been deprecated. Please use Create event (V4) instead. This operation creates a new event in a calendar. (V2)
Create event (V3) [DEPRECATED]	This action has been deprecated. Please use Create event (V4) instead. This operation creates a new event in a calendar.
Create event (V4)	This operation creates a new event in a calendar.
Delete contact (V2)	This operation deletes a contact from a contacts folder.
Delete contact [DEPRECATED]	This action has been deprecated. Please use Delete contact (V2) instead. This operation deletes a contact from a contacts folder.
Delete email (V2)	This operation deletes an email by id.
Delete email [DEPRECATED]	This action has been deprecated. Please use Delete email (V2) instead. This operation deletes an email by id.
Delete event (V2)	This operation deletes an event in a calendar.
Delete event [DEPRECATED]	This action has been deprecated. Please use Delete event (V2) instead. This operation deletes an event in a calendar.
Draft an email message	This operation drafts an email message.
Export email (V2)	Export the content of the email in the EML file format.
Export email [DEPRECATED]	This action has been deprecated. Please use Export email (V2) instead. Export the content of the email.
Find meeting times (V2)	Find meeting time suggestions based on organizer, attendee availability, and time or location constraints
Find meeting times [DEPRECATED]	This action has been deprecated. Please use Find meeting times (V2) instead. Find meeting time suggestions based on organizer, attendee availability, and time or location constraints
Flag email (V2)	This operation updates an email flag.
Flag email [DEPRECATED]	This action has been deprecated. Please use Flag email (V2) instead. This operation flags an email.
Forward an email (V2)	Forward an email.
Forward an email [DEPRECATED]	This action has been deprecated. Please use Forward an email (V2) instead. Forward an email.
Get Attachment (V2)	This operation gets an email attachment by id.
Get attachment [DEPRECATED]	This action has been deprecated. Please use Get Attachment (V2) instead. This operation gets an email attachment by id.
Get calendar view of events (V2) [DEPRECATED]	This action has been deprecated. Please use Get calendar view of events (V3) instead. This operation gets all events (including instances of recurrences) in a calendar. Recurrence property is null in this case.
Get calendar view of events (V3)	This operation gets all events (including instances of recurrences) in a calendar using Graph API. Recurrence property is null in this case.
Get calendar view of events [DEPRECATED]	This action has been deprecated. Please use Get calendar view of events (V3) instead. Get calendar view of events.
Get calendars (V2)	This operation lists available calendars.
Get calendars [DEPRECATED]	This action has been deprecated. Please use Get calendars (V2) instead. This operation lists available calendars.
Get contact (V2)	This operation gets a specific contact from a contacts folder.
Get contact [DEPRECATED]	This action has been deprecated. Please use Get contact (V2) instead. This operation gets a specific contact from a contacts folder.
Get contact folders (V2)	This operation lists available contacts folders using Graph API
Get contact folders [DEPRECATED]	This action has been deprecated. Please use Get contact folders (V2) instead. This operation lists available contacts folders.
Get contacts (V2)	This operation gets contacts from a contacts folder.
Get contacts [DEPRECATED]	This action has been deprecated. Please use Get contacts (V2) instead. This operation gets contacts from a contacts folder.
Get email (V2)	This operation gets an email by id.
Get email [DEPRECATED]	This action has been deprecated. Please use Get email (V2) instead. This operation gets an email by id.
Get emails (V2) [DEPRECATED]	This action has been deprecated. Please use Get emails (V3) instead. This operation gets emails from a folder.
Get emails (V3)	This operation gets emails from a folder via graph apis. Please note that filtering related to these fields: To, Cc, To Or Cc, From, Importance, Fetch Only With Attachments, Subject Filter, is performed using first 250 emails in a given mail folder. To avoid that limitation you can use 'Search Query' field and search the entire folder.
Get emails [DEPRECATED]	This action has been deprecated. Please use Get emails (V3) instead. This operation gets emails from a folder.
Get event (V1) [DEPRECATED]	This action has been deprecated. Please use Get event (V3) instead. This operation gets a specific event from a calendar. (V1)
Get event (V2) [DEPRECATED]	This action has been deprecated. Please use Get event (V3) instead. This operation gets a specific event from a calendar. (V2)
Get event (V3)	This operation gets a specific event from a calendar using Graph API. (V3)
Get events (V1) [DEPRECATED]	This action has been deprecated. Please use Get events (V4) instead. This operation gets events from a calendar. (V1)
Get events (V2) [DEPRECATED]	This action has been deprecated. Please use Get events (V4) instead. This operation gets events from a calendar. (V2)
Get events (V3) [DEPRECATED]	This action has been deprecated. Please use Get events (V4) instead. This operation gets events from a calendar. (V3)
Get events (V4)	This operation gets events from a calendar using Graph API. (V4)
Get mail tips for a mailbox (V2)	Get mail tips for a mailbox such as automatic replies / OOF message or if the mailbox is full. This is not available in GccHigh and Mooncake.
Get mail tips for a mailbox [DEPRECATED]	This action has been deprecated. Please use Get mail tips for a mailbox (V2) instead. Get mail tips for a mailbox such as automatic replies / OOF message or if the mailbox is full.
Get Outlook category names	This operation gets Outlook category display names.
Get room lists (V2)	Get all the room lists defined in the user's tenant
Get room lists [DEPRECATED]	This action has been deprecated. Please use Get room lists (V2) instead. Get all the room lists defined in the user's tenant
Get rooms (V2)	Get all the meeting rooms defined in the user's tenant
Get rooms [DEPRECATED]	This action has been deprecated. Please use Get rooms (V2) instead. Get all the meeting rooms defined in the user's tenant
Get rooms in room list (V2)	Get the meeting rooms in a specific room list
Get rooms in room list [DEPRECATED]	This action has been deprecated. Please use Get rooms in room list (V2) instead. Get the meeting rooms in a specific room list
Mark as read [DEPRECATED]	This action has been deprecated. Please use Mark as read or unread (V3) instead. This operation marks an email as having been read.
Mark as read or unread (V2) [DEPRECATED]	This action has been deprecated. Please use Mark as read or unread (V3) instead. This operation marks an email as read/unread.
Mark as read or unread (V3)	This operation marks an email as read/unread.
Move email (V2)	This operation moves an email to the specified folder within the same mailbox.
Move email [DEPRECATED]	This action has been deprecated. Please use Move email (V2) instead. This operation moves an email to the specified folder within the same mailbox.
Reply to email (V2) [DEPRECATED]	This action has been deprecated. Please use Reply to email (V3) instead. This operation replies to an email.
Reply to email (V3)	This operation replies to an email.
Reply to email [DEPRECATED]	This action has been deprecated. Please use Reply to email (V3) instead. This operation replies to an email.
Respond to an event invite (V2)	Respond to an event invite.
Respond to an event invite [DEPRECATED]	This action has been deprecated. Please use Respond to an event invite (V2) instead. Respond to an event invite.
Send a Draft message	This operation sends a Draft message.
Send an email (V2)	This operation sends an email message.
Send an email [DEPRECATED]	This action has been deprecated. Please use Send an email (V2) instead. This operation sends an email message.
Send an email from a shared mailbox (V2)	This operation sends an email from a shared mailbox. Your account should have permission to access the mailbox for this operation to succeed.
Send an email from a shared mailbox [DEPRECATED]	This action has been deprecated. Please use Send an email from a shared mailbox (V2) instead. This operation sends an email from a shared mailbox. Your account should have permission to access the mailbox for this operation to succeed.
Send an HTTP request	Construct a Microsoft Graph REST API request to invoke. These segments are supported: 1st segement: /me, /users/<userId> 2nd segment: messages, mailFolders, events, calendar, calendars, outlook, inferenceClassification. Learn more: https://docs.microsoft.com/en-us/graph/use-the-api.
Send approval email	This operation sends an approval email and waits for a response from the recipient. Please refer to the following link regarding the support of actionable messages in different mail clients: https://docs.microsoft.com/outlook/actionable-messages/#outlook-version-requirements-for-actionable-messages.
Send email with options	This operation sends an email with multiple options and waits for the recipient to respond back with one of the options. Please refer to the following link regarding the support of actionable messages in different mail clients: https://docs.microsoft.com/outlook/actionable-messages/#outlook-version-requirements-for-actionable-messages.
Set up automatic replies (V2)	Set the automatic replies setting for your mailbox.
Set up automatic replies [DEPRECATED]	This action has been deprecated. Please use Set up automatic replies (V2) instead. Set the automatic replies setting for your mailbox.
Update contact (V2)	This operation updates a contact in a contacts folder.
Update contact [DEPRECATED]	This action has been deprecated. Please use Update contact (V2) instead. This operation updates a contact in a contacts folder.
Update event (V1) [DEPRECATED]	This action has been deprecated. Please use Update event (V4) instead. This operation updates an event in a calendar. (V1)
Update event (V2) [DEPRECATED]	This action has been deprecated. Please use Update event (V4) instead. This operation updates an event in a calendar. (V2)
Update event (V3) [DEPRECATED]	This action has been deprecated. Please use Update event (V4) instead. This operation updates an event in a calendar.
Update event (V4)	This operation updates an event in a calendar using Graph API.
Update my contact's photo	Updates the photo of the specified contact of the current user. The size of the photo must be less than 4 MB.
Updates an email Draft message	This operation updates an an email Draft message.

Assign a category to multiple emails

Assigns an Outlook category

Create contact (V2)

Create contact [DEPRECATED]

Create event (V1) [DEPRECATED]

Create event (V2) [DEPRECATED]

Create event (V3) [DEPRECATED]

Create event (V4)

Delete contact (V2)

Delete contact [DEPRECATED]

Delete email (V2)

Delete email [DEPRECATED]