Welcome to Office 365 APIs | Microsoft Docs
Skip to main content

Office 365 APIs

This site contains the documentation for Office 365 REST APIs exposed on the OneNote and Outlook endpoints. The documentation is no longer actively updated. It is here for your reference, in case you have already included any of the API in your project.

Office 365 services, such as OneNote, Outlook, Excel, OneDrive, Microsoft Teams, Planner, and SharePoint, are now exposed in Microsoft Graph. Microsoft Graph is a unified API endpoint for accessing data across Microsoft 365, which includes Office 365, Enterprise Mobility, and Security and Windows services. It provides a simplified developer experience, with one endpoint and a single authentication token that gives your app access to data across all these services.

Our recommendation:

  • If you are starting a new app, please use Microsoft Graph.
  • If you are maintaining an existing project, use this documentation set for reference. In addition, plan your move to the latest APIs in Microsoft Graph to take advantage of all the new functionality and innovation there.
  • If you are adding new functionality to an existing project, integrate that new functionality by using Microsoft Graph.

With Microsoft Graph, you can access Office 365 data and more, from solutions across mobile, web, and desktop platforms. So whether you're building web applications by using .NET, PHP, Java, Python, or Ruby on Rails, or creating apps for the Universal Windows Platform (UWP), iOS, Android, or on another device platform, it's your choice.

In this section

 none
Is it possible to create multiple non-block tasks in SharePoint designer? RRS feed

  • Question

  • I have a workflow that needs to send out multiple non-related tasks at once. I want it to go like this:

    - send task to user A

    - send task to user B

    - send task to user C

    - wait for Status on list item to change

    - send task to user D

    I want to send tasks to user A, B, and C simultaneously, but currently it sends out the task to user A and waits for that task to complete before sending out the task to user B. I'm currently using the To-Do task. Is there a way to create a task that doesn't block? The only thing I can think of doing is creating a separate workflow for each task, but that will be a pain because I will need to create probably 7 workflows each of which will run on every change to the list item and I will have to create multiple tracking fields as well to track if a task was already created or not. I'm just hoping for an easier way.

    Friday, January 27, 2017 9:35 PM

All replies

  • Hi KubalaML,

    From your description, you want to send tasks to user A, B, and C simultaneously.

    Do not use the "Assign a To-do item" action.

    Using the "Start Custom Task Process" action, Choose Parallel (all at once):

    Best Regards,

    Lisa Chen


    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com

    • Proposed as answer by croute1 Monday, January 30, 2017 2:25 PM
    Monday, January 30, 2017 1:02 PM
    Moderator
  • Yeah I was thinking of a way to get that to work, but it's not quite what I need. Each user has a different task with their own set of instructions. It's not three identical tasks.
    Monday, January 30, 2017 11:00 PM
  • Hi,

    How did you achieved the scenario. I am facing same kind of challenge!

    Wednesday, August 28, 2019 9:59 AM
Welcome to Office 365 APIs | Microsoft Docs
Skip to main content

Office 365 APIs

This site contains the documentation for Office 365 REST APIs exposed on the OneNote and Outlook endpoints. The documentation is no longer actively updated. It is here for your reference, in case you have already included any of the API in your project.

Office 365 services, such as OneNote, Outlook, Excel, OneDrive, Microsoft Teams, Planner, and SharePoint, are now exposed in Microsoft Graph. Microsoft Graph is a unified API endpoint for accessing data across Microsoft 365, which includes Office 365, Enterprise Mobility, and Security and Windows services. It provides a simplified developer experience, with one endpoint and a single authentication token that gives your app access to data across all these services.

Our recommendation:

  • If you are starting a new app, please use Microsoft Graph.
  • If you are maintaining an existing project, use this documentation set for reference. In addition, plan your move to the latest APIs in Microsoft Graph to take advantage of all the new functionality and innovation there.
  • If you are adding new functionality to an existing project, integrate that new functionality by using Microsoft Graph.

With Microsoft Graph, you can access Office 365 data and more, from solutions across mobile, web, and desktop platforms. So whether you're building web applications by using .NET, PHP, Java, Python, or Ruby on Rails, or creating apps for the Universal Windows Platform (UWP), iOS, Android, or on another device platform, it's your choice.

In this section