01-05-2021



-->

  1. Microsoft Planner Desktop App
  2. Office 365 Tasks Desktop App
  3. Office 365 Tasks Ios
  4. Office 365 Tasks Api
  5. Office 365 Tasks Iphone
  • Your tasks, events, and meetings can all get mixed up and make your display messy and hard to follow. It takes a lot of effort, even with some training, to arrange your tasks and make each one clear. Office 365 Planner. Planner is the heart of the Office 365 project management toolset.
  • Tasks can also be created from the To-Do Bar and by dragging an email message to the Tasks folder. How to Repeat Outlook Tasks. To repeat a task created in Microsoft Outlook: Set a reminder for the first occurrence of the task. Pick Recurrence from the Task tab. Define the Task Recurrence pattern such as the 1st day of the month or every Wednesday.

Applies to: Configuration Manager (current branch)

Gain a competitive advantage by linking all your data. Connect workflows to hundreds of data sources using a library of connectors and Microsoft Dataverse —bringing your data together for a single source of truth while you uncover insights as well as customize and extend Microsoft 365, Dynamics 365, and Azure capabilities.

Note

Systemverilog operators. Starting on April 21, 2020, Office 365 ProPlus is being renamed to Microsoft 365 Apps for enterprise. For more information, see Name change for Office 365 ProPlus. You may still see references to the old name in the Configuration Manager console and supporting documentation while the console is being updated.

Beginning in Configuration Manager version 1802, you can review Microsoft 365 Apps client information from the Office 365 Client Management dashboard. The Office 365 client management dashboard displays a list of relevant devices when graph sections are selected.

Prerequisites

Enable hardware inventory

The data that is displayed in the Office 365 Client Management dashboard comes from hardware inventory. Enable hardware inventory and select the Office 365 Configurations hardware inventory class for data to display in the dashboard.

  1. Enable hardware inventory, if it isn't yet enabled. For details, see Configure hardware inventory.
  2. In the Configuration Manager console, navigate to Administration > Client Settings > Default Client Settings.
  3. On the Home tab, in the Properties group, click Properties.
  4. In the Default Client Settings dialog box, click Hardware Inventory.
  5. In the Device Settings list, click Set Classes.
  6. In the Hardware Inventory Classes dialog box, select Office 365 Configurations.
  7. Click OK to save your changes and close the Hardware Inventory Classes dialog box.

The Office 365 Client Management dashboard starts displaying data as hardware inventory is reported.

Connectivity for the top-level site server

(Introduced in version 1906 as a prerequisite)

Your top-level site server needs access to the following endpoint to download the Microsoft Apps 365 readiness file:

  • Starting March 2, 2021: https://omex.cdn.office.net/mirrored/sccmreadiness/SOT_SCCM_AddinReadiness.CAB
    • Location prior to March 2, 2021: https://contentstorage.osi.office.net/sccmreadinessppe/sot_sccm_addinreadiness.cab

Note

  • The location of this file is changing March 2, 2021. For more information, see Download location change for Microsoft 365 Apps readiness file.
  • Internet connectivity isn't required for the client devices for any of these scenarios.

Enable data collection for Microsoft 365 Apps

(Introduced in version 1910 as a prerequisite)

Starting in version 1910, you'll need to enable data collection for Microsoft 365 Apps to populate information in the Office 365 Pilot and Health Dashboard. The data is stored in the Configuration Manager site database and not sent to Microsoft.

This data is different from the diagnostic data, which is described in Diagnostic data sent from Microsoft 365 Apps to Microsoft.

You can enable data collection either by using Group Policy or by editing the registry.

Enable data collection from Group Policy

  1. Download the latest Administrative Template files from the Microsoft Download Center.
  2. Enable the Turn on telemetry data collection policy setting under User ConfigurationPoliciesAdministrative TemplatesMicrosoft Office 2016Telemetry Dashboard.
    • Alternatively, apply the policy setting with the Office cloud policy service.
    • The policy setting is also used by the Office Telemetry Dashboard, which you don't need to deploy for this data collection.

Enable data collection from the registry

The command below is an example of how to enable the data collection from the registry:

Viewing the Office 365 Client Management dashboard

To view the Office 365 Client Management dashboard in the Configuration Manager console, go to Software Library > Overview > Office 365 Client Management. At the top of the dashboard, use the Collection drop-down setting to filter the dashboard data by members of a specific collection. Beginning in Configuration Manager version 1802, the dashboard displays a list of relevant devices when graph sections are selected.

The Office 365 Client Management dashboard provides charts for the following information:

  • Number of Microsoft 365 Apps clients
  • Microsoft 365 Apps client versions
  • Microsoft 365 Apps client languages
  • Microsoft 365 Apps client channelsFor more information, see Overview of update channels for Microsoft 365 Apps.

Integration for Microsoft 365 Apps readiness

Starting in Configuration Manager version 1902, you can use the dashboard to identify devices with high confidence that are ready to upgrade to Microsoft 365 Apps. This integration provides insights into potential compatibility issues with add-ins and macros in your environment. Then use Configuration Manager to deploy Microsoft 365 Apps to ready devices.

The Office 365 client management dashboard includes a tile, Office 365 Apps Upgrade Readiness. This tile is a bar chart of devices in the following states:

  • Not assessed
  • Ready to upgrade
  • Needs review

Select a state to drill-through to a device list. This readiness report shows more detail about devices. It includes columns for the compatibility state of both add-ins and macros.

Prerequisites for Microsoft 365 Apps readiness integration

  • Enable hardware inventory in client settings. For more information, see the Prerequisites section.

  • The device needs connectivity to the Office content delivery network (CDN) to download an add-in readiness file. For more information, see Content delivery networks. If the device can't download this file, the add-ins state is Needs review.

    Note

    No data is sent to Microsoft for this feature.

Detailed macro readiness

By default, the scanning agent looks at the most recently used (MRU) files list on each device. It counts the files in this list that support macros. These files include the following types:

  • Macro-enabled Office file formats, such as Excel macro-enabled workbooks (.xlsm) or Word macro-enabled document (.docm)
  • Older Office formats that don't indicate whether there's macro content. For example, an Excel 97-2003 workbook (.xls).

If you need more detailed information about macro compatibility, deploy the Readiness Toolkit for Office to analyze the code within the macro files. It checks if there are any potential compatibility concerns. For example, the file uses a function that changed in a more recent version of Office. After you run the Readiness Toolkit for Office and select the option for Most recently used Office documents and installed add-ins on this computer, or use the -mru flag in the command line, the results can be picked up by Configuration Manager's hardware inventory agent. This additional data enhances the device readiness calculation. For more information, see Use the Readiness Toolkit for Office to assess application compatibility for Microsoft 365 Apps.

Note that the Readiness Toolkit does not need to be installed on every target device in order to carry out the scan. You can use the sample command line option below to scan each desired device. The output flag is required, but the files will not be used to generate the results in the dashboard, so any valid location can be selected.

For more information, see Getting readiness information for multiple users in an enterprise.

Microsoft 365 Apps readiness dashboard

(Introduced in version 1906)

To help you determine which devices are ready to upgrade to Microsoft 365 Apps, there's a readiness dashboard starting in version 1906. It includes the Office 365 Apps Upgrade Readiness tile that released in Configuration Manager current branch version 1902. The following new tiles on this dashboard help you evaluate add-in and macro readiness:

  • Deployment
  • Device readiness
  • Add-in readiness
  • Add-in support statements
  • Top add-ins by count of version
  • Number of devices that have macros
  • Macro readiness
  • Macro advisories

The following video is a session from Ignite 2019, which includes more information:

Using the Microsoft 365 Apps upgrade readiness dashboard

After verifying you have the prerequisites, use the following instructions to use the dashboard:

  1. In the Configuration Manager console, go to the Software Library workspace, expand Office 365 Client Management.
  2. Select the Microsoft 365 Apps Upgrade Readiness node.
  3. Change the Collection and Target Office Architecture to change the information relayed in the dashboard.

Device Readiness information

Once the add-in and macro inventory on each device is evaluated, the devices are then grouped according to the information. Devices whose status are listed as Ready to upgrade aren't likely to have any compatibility issues.

Selecting the Ready to upgrade category on the graph shows more details about the devices in the limiting collection. You can review the device list, make selections according to your business requirements, and create a new device collection from your selection. Use your new collection to deploy Microsoft 365 Apps with Configuration Manager.

Devices that might be at risk for compatibility issues are marked as Needs review. These devices may need action to be taken before upgrading them to Microsoft 365 Apps. For example, you might update critical add-ins to a more recent version.

Add-in information

On each device, an inventory of all installed add-ins is collected. The inventory is then compared with the information Microsoft has about the add-in performance on Microsoft 365 Apps. If an add-in is found which is likely to cause issues after upgrading, then all devices with the add-in are flagged for review.

Macro information

Configuration Manager looks at the most recently used files on each device. It counts the files in this list that support macros, including the following types:

  • Macro-enabled Office file formats.
  • Older Office formats, which don't indicate if there's macro content.

This report can be used to identify which devices have recently used files which may contain macros. The Readiness Toolkit for Office can then be deployed using Configuration Manager to scan any devices where more detailed information is needed, and check if there are any potential compatibility concerns. For example, if the file uses a function that changed in a more recent version of Microsoft 365 Apps.

For more information about how to carry out the scan, see Detailed macro readiness.

365

Tip

Macro inventory is populated by default based on the document extensions in the MRU. Macro compatibility and macro status are populated once the Readiness Toolkit for Office scan runs on the device.

Office 365 Pilot and Health dashboard

(Introduced in version 1910)

Microsoft Planner Desktop App

Starting in version 1910, the Office 365 Pilot and Health Dashboard helps you plan, pilot, and perform your Microsoft 365 Apps deployment. The dashboard provides health insights for devices with Microsoft 365 Apps to help identify possible issues that may affect your deployment plans. The Office 365 Pilot and Health Dashboard provides a recommendation for pilot devices based on add-in inventory. The following tiles are in the dashboard:

  • Generate pilot
  • Recommended pilot devices
  • Deploy pilot
  • Devices sending health data
  • Devices not meeting health goals
  • Add-ins not meeting health goals
  • Macros not meeting health goals

Using the Office 365 Pilot and Health dashboard

After verifying you have the prerequisites, use the following instructions to use the dashboard:

  1. In the Configuration Manager console, go to the Software Library workspace, expand Office 365 Client Management.
  2. Select the Office 365 Pilot and Health node.

Generate pilot

Generate a pilot recommendation from a limiting collection at the click of a button. As soon as the action is launched, a background task starts calculating your pilot collection. Your limiting collection must contain at least one device with an Office version that isn't Office 365 Apps.

Recommended pilot devices

Recommended pilot devices are a minimal set of devices representing all installed add-ins across the limiting collection you used when generating the pilot. Drill down to get a list of these devices. Then use the details to exclude any devices from the pilot if needed. If all of your add-ins are already on Microsoft 365 Apps devices, then devices with those add-ins won't be included in the calculation. This also means it's possible that you won't get any results in your pilot collection since all of your add-ins have been seen on devices where Microsoft 365 Apps is installed.

Deploy pilot

Once you accept your pilot devices, deploy Microsoft 365 Apps to the pilot collection using the phased deployment wizard. Admins can define the pilot and limiting collection in the wizard to manage deployments.

Health data

Once Microsoft 365 Apps is installed, enable health data on your pilot devices. The health data gives you insight into which add-ins and macros don't meet health goals. The Devices ready to deploy chart identifies non-pilot devices that are ready for deployment by using the health insights. Get a count of devices that are sending health data from the Devices sending health data chart.

Devices not meeting health goals

This tile summarizes devices that have issues with add-ins, macros, or both.

Add-ins not meeting health goals

  • Load failures: The add-in failed to start.
  • Crashes: The add-in failed while it was running.
  • Error: The add-in reported an error.
  • Multiple issues: The add-in has more than one of the above issues.

Macros not meeting health goals

Office 365 tasks app
  • Load failures: The document failed to load.
  • Runtime errors: An error happened while the macro was running. These errors can be dependent on the inputs so may not always occur.
  • Compile errors: The macro didn't compile correctly so it won't attempt to run.
  • Multiple issues: The macro has more than one of the above issues.

Note

Macro inventory is populated by data from the Readiness Toolkit for Office and recently used data files. Macro health is populated by health data. Due to the different data sources, it's possible for the macro health status to be Needs review when the macro inventory is Not scanned.

Known issues

There is a known issue with the Deploy Pilot tile. At this time it can't be used to deploy to a pilot. The workaround is the existing workflow for deploying an application using the Phased Deployment Wizard.

Next steps

Everything is a project! This is my main motto in life. Hey, after all, to get things done, we need to complete tasks. While, for the most part, we use SharePoint and Office 365 to store documents, the second most important function of our daily routine is to track and complete tasks. Tasks for temporary project teams we are part of, tasks for departments and business units, personal tasks. I have written a number of posts lately on various tools that we have now in Office 365. With this article, I would like to revisit the topic and summarize all the available task management options in SharePoint and Office 365 in a single article.

Option 1: Tasks Web Part

Office 365 Tasks Desktop App

The first option is to use the good-old Tasks Web Part in SharePoint. While it may be considered old-fashioned compared to other options we now have, it is still a viable option as it allows you to create own metadata, send emails to those Assigned to the task as well as integrate with MS Project. I provided an overview of its features and capabilities here.

Office 365 Tasks Ios

Option 2: Planner

The option that was like a breath of fresh air was when Planner became available in Office 365. Unlike the task list above, Planner was a much more visual, light-weight task management solution, suitable mostly for agile/informal projects. I extensively documented the significant differences between the Task List and Planner here.

Planner is part of an Office 365 Group, and I also documented this important principle here.

Option 3: Microsoft To Do

This is a new kid on the block as far as task management options. Think of it as a Planner but for personal tasks. Just like Planner, it is entirely web-based, and on top of it – it also integrates with Planner pulling all the tasks assigned to you in one spot! I explained To Do in greater detail here.

Option 4: Project for the Web

This is one of the latest major additions to the vault of available task management tools. Project for the Web allows users to manage complicated projects in an MS Project style capacity, but on the web and under the umbrella of an Office 365 Group, just like Planner. As time goes by, I am sure it will get additional features that it will inherit from its older brother we always had – the desktop version of MS Project. If you want to learn more about the tool, please reference this post.

Office 365 Tasks Api

Option 5: Project Online

Office 365 Tasks Iphone

Last but not least, the elephant in the room when it comes to task management options in SharePoint and Office 365 – Project Online. This one was and still is the best option for hardcore Project/Portfolio Management. This tool allows you to aggregate multiple project plans, manage tasks, and resources for a portfolio of projects. I blogged about the tool earlier. This tool is a bit outdated by now, but I am sure it is a matter of time before Microsoft modernizes it, just like they did with Project for the Web above.