Microsoft Planner–a few common support answers


Today sees the start of General Availability of Microsoft Planner, known during the First Release preview as Office 365 Planner.  It may take a few weeks until it is fully rolled out so please be patient if you are not seeing Planner yet.  Based on some of the questions we have already seen in preview we have an FAQ document , but wanted to give a little more detail in this blog post and also some examples of the things I expect you might need to know.

*** 6/8/2016 – Once you have read this I did follow up with a few more details in a new blog here. – which now includes new information added 10/7/2016***

Firstly if you have been in First Release thanks for trying out Planner – but you will now see that Planner, rather than being a top level license that you needed to assign, is now part of your Office 365 plan (such as E3, E5 etc.) and is listed under that license – and is enabled by default.

In my screenshot below I have both the First Release (300,000) and the E3 licenses assigned (and mine still shows Office365 Planner – it will be changing to Microsoft Planner shortly).

image

The KB article to automate the license assignment using PowerShell has been updated and now includes a section for handling the plan level licenses – see the foot of https://support.microsoft.com/en-us/kb/3108269 and note specifically that the ‘DisabledPlans’ parameter if you need to remove licenses for Planner is “PROJECTWORKMANAGEMENT”.  One question that comes up is how do I know what new features might be coming so that I can add the addition DisabledPlans to my PowerShell commands used for user and license management?  I found an interesting approach to this which sets the plans you do want and then uses PowerShell to work out which ones aren’t in your list – see http://mattmcnabb.github.io/Office-365-Licensing_4 for more details.  I’m certainly not trying to discourage you from using Planner – but do appreciate that with large organizations you do sometimes need to plan how you want things used before jumping in.

If you haven’t used Planner during the First Release Preview then you can find the product details here and also great information for admins to guide you on your journey with Planner – which also includes useful links for end users – and the announcement blog post at https://blogs.office.com/2016/06/06/microsoft-planner-ready-for-showtime/.  A direct link to the admin FAQ here.

Planner makes use of Office 365 Groups – so each plan is a group – and when you create a plan it creates a group.  The Group then supports the collaboration features by providing storage for attachments and also a mailbox for group discussions.  Planner will give you the best experience if you also have your e-mail in Office 365 (Exchange Online) – but you can still use Planner even if you have on-premises Exchange.  A couple of the features you will miss will be the ability to comment and also makes plans favorites within OWA – but you can still do this in Planner itself.

Regarding Groups we have had some feedback from First Release customers that they wish to have more central control of group creation – and prefer that not everyone can create groups.  It is possible to do this and we have some new PowerShell capabilities to support this.  The article at https://msdn.microsoft.com/en-us/library/jj151815.aspx (thanks Jürgen!)  will help you – but basically you can disable group creation for everyone – then create an AD group containing the individuals who you allow to create groups – then set this group as the ‘allowed list’ via PowerShell.  These are the steps I used when I tested this.

First you will need the latest Public Preview Azure AD PowerShell stuff – available at the time of writing from this link – http://connect.microsoft.com/site1164/Downloads/DownloadDetails.aspx?DownloadID=59185.

You will also need to have created an AD Group in Azure and added users who you need to create groups.  Azure AD can be found in the Office 365 Admin portal – under Admin.  If you haven’t used it before it takes a couple of minutes to set up.  You can navigate to your Active Directly domain (it takes you out of the new UI and back to the ‘Classic’ UI at this point then click Groups and you can add a new AD group (we are not talking Office 365 groups at this point…) using ADD GROUP at the foot of the page.  The type should be Office 365. Once created then add your users and note the Object ID by going to Properties (You will need this later).  Here is what mine looks like – and I called it cancreategroups:

image

Now in the Microsoft Azure Active Directly Module for PowerShell we can use the following commands to set the group creation to disabled and the group holding our list of allowed users:

Connect-MsolService
$template = Get-MsolSettingTemplate –TemplateId 62375ab9-6b52-47ed-826b-58e47e0e304b
$setting = $template.CreateSettingsObject()
$setting[“EnableGroupCreation”] = “false”
$setting[“GroupCreationAllowedGroupId”] = “7edd1d0b-557d-43e6-b583-4f3e0198c167”
New-MsolSettings –SettingsObject $setting

Walking you through these, the first line will prompt for credentials to connect you to your service.  The second line will get you a reference to the Group.Unified template – the GUID is constant I think – but you can always run Get-MsolAllSettingTemplate to see if this is correct in your case.  We are then making the actual settings – EnableGroupCreation to False and setting the GUID of our AD group noted above as the GroupCreationAllowedGroupId.  Finally we are applying our setting object.  You can refer to the PDF at the same download location as the Azure AD PowerShell for more details – and you may need to edit an existing Settings object rather than creating a new one like I have.  One way to check your settings is to use the Graph Explorer https://graph.microsoft.io/en-us/ – just click the Try the API, sign in, enter a URL of  https://graph.microsoft.com/beta/settings (after choosing the beta ‘version’) and your should see something like this:

image

You could use the same API to make the settings rather than using PowerShell, but I don’t have the examples to hand yet.

And no need to add certain admins to the group as certain roles in Office 365 will still be able to create Office 365 Groups regardless of the settings above:

  • Company Administrator
  • User Account Administrator
  • Mailbox Administrator
  • Partner Tier1 Support
  • Partner Tier2 Support
  • Directory Writers

We would welcome feedback on the exclusion of these roles from the group control rules.

After setting up the settings above then logging in as a user not in the ‘allowed’ group then when I then tried to create a Group I got this message:

image

When I tried to create a Plan – it was slightly less informative – giving the message:

image

We have a different error message in the pipeline – but if you users do report this it may well be that group creation is blocked for that user and it will not work even if they do wait.

A couple of other points for now – and the first relates to different behaviors depending on the location of your mailbox (and if you don’t know then ask your administrator.  If you don’t have your mailbox in Exchange Online then you will not be able to interact with Comments nor add favorite plans from within Outlook Web App or Outlook – but working within Planner should work fine. *** Adding KB – https://support.microsoft.com/en-us/kb/3169632 – thanks Bill! ***

Final point – and we have had a few reports of an apparent difference in behavior of the ‘Attach’ link on the Task pane depending on how you navigate to the pane.  If you go via the Planner hub and drill down to a task then the Attach link is active:

image

If however I navigate via My tasks the Attach link is not active.

image

This is expected behavior as the context of the Plan gives access to the Group storage for attachments – whereas in the context just of the task this isn’t the case.  It feels a little odd – but there are some very valid reasons why we do this.


Comments (79)

  1. Steven Collier says:

    Can the group granted permission be a Dynamic Group ?

    1. Hi Steven, The groups needs to be an AD Group – so in my example I created in Azure AD, but it could also be a Unified Group – as they show up in AD too. However, if you mean a Dynamic distribution group then I don’t think these are the right sort of ‘groups’. Also to add to the detail if you create a Unified Group – for example in OWA – then you can find the Object ID using Get-MsolGroup. Get-MsolGroup does not return distribution groups. I’m sure someone will correct me if I have this wrong – this is all pretty new.
      Best regards,
      Brian.

  2. Peter Kruisman says:

    Hi Brian,
    We have created a naming policy for Groups. When we create a group using outlook then this policy is applied to the prefix. (Groups-groupname)
    Planner on the other hand ignores the policy. Is this a known issue?

    1. Hi Peter, yes this is a current limitation and I will find out timescales for this to be honored by the Graph API. It is expected soon.
      Best regards,
      Brian.

      1. Peter Kruisman says:

        Good to know that this is recognized by the Planner team. Will you post here the timescale?
        Regards Peter

        1. Drew Madelung says:

          Does the naming policy also not work when creating groups through Power BI?

          1. Not my specific area of expertize Drew – but I believe they rely on the same API as Planner – so until the API enforces the policy Power BI is probably similarly affected.
            Best regards,
            Brian

  3. Chuck Boeheim says:

    To me, the most egregious thing that Planner does is create SharePoint sites in the enterprise-wide /sites/ directory that are *INVISIBLE* to the SharePoint admin. So a group decides to make an Engineering planning group, and then the Engineering school requests a SharePoint site by that name, resulting in a mysterious failure. This demonstrates a failure of understanding on Microsoft’s part of how a large organization works. Given Microsoft’s size, this is baffling.

    1. Thanks for the feedback Chuck – I’ll certainly make sure that this gets back to the product group. Hopefully when the API control for Group naming comes into force that could give one way to avoid clashes, but I do fully understand your concerns.
      Best regards,
      Brian

      1. Chuck Boeheim says:

        Thank you, I appreciate you taking the feedback. I think it’s also important to give the SharePoint admin more visibility into what’s going on. As enterprises we need to understand how our services are being used and report on that usage. I was glad to see that at least when you knew that name of the group, you could do Get-SPOSite on that and get information about it, just disappointed that they were normally invisible and undiscoverable.

      2. timothywgray says:

        Another concern is that SharePoint sites are being created under the SITES directory without any branding. Is there anyway to apply branding automatically to these sites? We use exclusively CSS to brand our sites. Can a CSS be applied to these newly-created sites automatically? Because I see no way that I can convince all of these newly-minted site owners to log in and put a CSS on these locations. The net results will be a large number of locations under our domain without the necessary branding, which, to quote Mr. Boeheim, will be baffling.

        1. I’ll see what I can find out Timothy. The sites stuff comes from Groups rather than Planner directly – so not something I’ve looked into. But I know some people to ask…
          Best regards,
          Brian.

        2. Hi Timothy, this should be possible in the future once the feature Christophe mentioned in his blog is released – https://blogs.office.com/2016/06/13/whats-new-in-office-365-groups-administration-june-2016-update/ – “we plan to deliver the following key features in the second half of this year to continue helping you work across teams and organizations: the ability to add external members to a group, a SharePoint team site for every group “. The ability to use templates may not be available when the feature first releases – but will be coming. Expect to see this in the next few months.
          Best regards,
          Brian

  4. Joseph Jorgenson says:

    I am an EDU tenant admin and trying to restrict the creation to our Fac\Staff users, after installing the latest AzureAD Powershell I still do not have access to “Get-MsolSettingTemplate” or “New-MsolSettings” Does this only work for Azure AD Premium customers?

    1. Hi Joseph, this doesn’t need the Premium account – I’m running it my test tenant just with the ‘Access to Azure Active Directory’ subscription from my O365 account. What version do you see next to your commands if you do a gcm *msol*? I’m seeing 1.1.117.0.
      Best regards,
      Brian.

      1. Joseph Jorgenson says:

        Have it fixed now. Your post said the “Latest” version but what you meant is the “Latest Public Preview” version. I stay away from preview versions for our production systems but in the case of O365 it looks like I will need to change that policy. I was downloading from: http://social.technet.microsoft.com/wiki/contents/articles/28552.microsoft-azure-active-directory-powershell-module-version-release-history.aspx

        1. Glad you got it working Joseph – and sorry for the confusion – I’ll add the words ‘Public Preview’.
          Brian.

  5. Tony Cullen says:

    For some reason I keep getting the following error; same issue on 3 pc’s. gcm *msol* shows all modules at 1.1.117.0

    Get-MsolSettingTemplate : Error calling GetSettingTemplates:
    Content {
    “error”: {
    “code”: “Request_ResourceNotFound”,
    “message”: “Resource ‘request id removed …’ does not exist or one of its queried
    reference-property objects are not present.”,
    “innerError”: {
    “request-id”: “request id removed …”,
    “date”: “2016-06-08T10:33:26”
    }
    }

    ??

    1. Hi Tony – if you just run Get-MsolAllSettingTemplate do you see two templates returned? I’d expect two lines – one for the Group.Unified and one for Group.Unified.Guest. Just running Get-MsolSettingTemplate would require another parameter – to identify the template you wanted.
      Best regards,
      Brian.

      1. Tony Cullen says:

        Brian,

        All sorted; working fine now.

        many thanks.

        1. Vanl says:

          Thanks Brian. All was good until i tried to apply the setting. I got the error below, any suggestion?

          New-MsolSettings : Error calling CreateSettings:
          Content {
          “error”: {
          “code”: “Request_BadRequest”,
          “message”: “A conflicting object with one or more of the specified property values is present in the directory.”,
          “innerError”: {
          “request-id”: ” I removed the ID”,
          “date”: “2016-06-09T03:28:40”
          }
          }
          }
          ErrorException
          ErrorMessage
          StatusCode BadRequest
          StatusDescription Bad Request
          ResponseStatus Completed
          At line:1 char:1
          + New-MsolSettings -SettingsObject $setting
          + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
          + CategoryInfo : NotSpecified: (:) [New-MsolSettings], ApiException
          + FullyQualifiedErrorId : Microsoft.Online.Administration.Automation.ApiException,Microsoft.Online.Administration.
          Automation.CreateSettings

          1. Hi Vanl, my sample assumes you don’t have any settings configured. What do you see of you run Get-MsolAllSettings? You can pull up and existing setting with a Get and the ObjectIdand then edit the values – or as there are only a few I’ve tended to use the Remove-MsolSettings and start clean.
            Best regards,
            Brian.

          2. Vanl says:

            Thank you, that is my issue. Get-MsolAllSettings returned only one entry, the default value for Group.Unified…
            ObjectId DisplayName TemplateId Values
            ——– ———– ———- ——
            aa763c14-7dac-4859-bfa6-e42489531ba1 Group.Unified 62375ab9-6b52-47ed-826b-58e47e0e304b {GroupCreationAllowedGroupId, AllowToAddGu…

            i’ll try Remove-MsolSettings. Thanks again.
            Vanl

          3. Drew Madelung says:

            I tested using this script to remove these settings but users outside of the group that I tested with still cannot create groups after the settings were removed. Anyone else try to remove these settings?

            $settings = Get-MsolAllSettings | where-object {$_.displayname -eq “Group.Unified”}
            Remove-MsolSettings -SettingId $settings.ObjectId

          4. I’ll check again Drew, but pretty sure I ran through the scenario of removing the settings and things worked as expected.
            Best regards,
            Brian.

          5. I’ll do another post shortly – but just in case folks are following this thread, it does appear that if you Remove-MsolSettings -SettingsId then the previous settings are still enforced. You would need to modify the existing ones to allow group creation (and that will be the topic of my next blog post…)

  6. Garyth Stephens says:

    Hi Brian

    Do we need to allow time for this to replicate around the Office365 environment before this will start working?

    We have followed your instructions in our Test Tenant but have not been able to get it to work.

    Also do we have to touch the GroupCreationEnabled flag on the OWAMailboxPolicy? When it is set to False my test account is unable to create groups even though they are in the “Allow” group, and when it is set to true my test account is able to create groups regardless of it membership in the “Allow” group.

    I appreciate your help with this.

    1. This should be pretty instantaneous in being applied Garyth – at least in my experience. You would certainly need to also ensure the OWAMailboxPolicy didn’t conflict. This wouldn’t stop Planner from creating groups but would certainly stop Group natively. Can you confirm that the settings really are applied – either via Graph or using the following – and getting your setting ID from Get-MsolAllSettings:

      $v=Get-MsolSettings -SettingId
      $v.values

  7. Rick says:

    I haven’t upgraded from DirSync to Azure AD Connect as of yet. Will creating a Group of users in AD work with stopping users from creating group when they create a Planner as you stated in your example since I am using DirSync to sync user Office 365.

    1. I haven’t tried this Rick – but pretty sure this will need a Group that AAD recognized. If you navigate to AAD does this show the groups that you are using?
      Best regards,
      Brian.

  8. kishore says:

    New-MsolSettings –SettingsObject $setting

    Not able execute the Above Command

    New-MsolSettings : Error calling CreateSettings:
    Content {
    “error”: {
    “code”: “Request_BadRequest”,
    “message”: “A conflicting object with one or more of the specified property values is present in the directory.”,
    “innerError”: {
    “request-id”: “71060955-48ba-4fa2-be33-49926f358ebd”,
    “date”: “2016-07-26T19:38:15”
    }
    }
    }
    ErrorException
    ErrorMessage
    StatusCode BadRequest
    StatusDescription Bad Request
    ResponseStatus Completed
    At line:1 char:1
    + New-MsolSettings -SettingsObject $setting
    + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo : NotSpecified: (:) [New-MsolSettings], ApiException
    + FullyQualifiedErrorId : Microsoft.Online.Administration.Automation.ApiException,Microsoft.Online.Administration.Automation.CreateSettings

    1. Looks like you are trying to use ‘new-msolsetting’ when you already have a setting set. Either remove or edit the setting you have. Kishore.
      Best regards,
      Brian.

      1. Shaun Binkley says:

        Hi Brian,

        Exactly how do I edit or remove the setting I have? The error I see is as follows:

        Connect-MsolService
        $template = Get-MsolSettingTemplate –TemplateId 62375ab9-6b52-47ed-826b-58e47e0e304b
        $setting = $template.CreateSettingsObject()
        $setting[“EnableGroupCreation”] = “false”
        $setting[“GroupCreationAllowedGroupId”] = “91bb8baa-bf77-4e65-9aba-1dc206f80c7f”
        New-MsolSettings –SettingsObject $setting
        New-MsolSettings : Error calling CreateSettings:
        Content {
        “error”: {
        “code”: “Request_BadRequest”,
        “message”: “A conflicting object with one or more of the specified property values is present in the directory.”,
        “innerError”: {
        “request-id”: “26daebd6-3e22-4c55-ad6f-b624775a7312”,
        “date”: “2016-11-08T12:59:50”
        }
        }
        }
        ErrorException
        ErrorMessage
        StatusCode BadRequest
        StatusDescription Bad Request
        ResponseStatus Completed
        At line:6 char:1
        + New-MsolSettings –SettingsObject $setting
        + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
        + CategoryInfo : NotSpecified: (:) [New-MsolSettings], ApiException
        + FullyQualifiedErrorId : Microsoft.Online.Administration.Automation.ApiException,Microsoft.Online.Administration.Automation.CreateSettings

        The Microsoft Graph tool is fairly cool. I can see that we do have the following object right at the bottom of the list:

        {
        “@odata.context”: “https://graph.microsoft.com/beta/$metadata#settings”,
        “value”: [
        {
        “id”: “aafd6c49-b6c9-4cea-8800-65efd364e0e3”,
        “displayName”: “Group.Unified”,
        “templateId”: “62375ab9-6b52-47ed-826b-58e47e0e304b”,
        “values”: [
        {
        “name”: “PrefixSuffixNamingRequirement”,
        “value”: “”
        },
        {
        “name”: “AllowGuestsToBeGroupOwner”,
        “value”: “false”
        },
        {
        “name”: “AllowGuestsToAccessGroups”,
        “value”: “true”
        },
        {
        “name”: “GuestUsageGuidelinesUrl”,
        “value”: “”
        },
        {
        “name”: “GroupCreationAllowedGroupId”,
        “value”: “”
        },
        {
        “name”: “AllowToAddGuests”,
        “value”: “True”
        },
        {
        “name”: “UsageGuidelinesUrl”,
        “value”: “”
        },
        {
        “name”: “ClassificationList”,
        “value”: “”
        },
        {
        “name”: “EnableGroupCreation”,
        “value”: “true”
        }
        ]
        }
        ]
        }

        1. Shaun Binkley says:

          Sorted:

          Connect-MsolService
          $group = Get-MsolGroup -All | Where-Object {$_.DisplayName -eq “O365_Group_Create”}
          $settings = Get-MsolAllSettings | where-object {$_.displayname -eq “Group.Unified”}
          $singlesettings = Get-MsolSettings -SettingId $settings.ObjectId
          $value = $singlesettings.GetSettingsValue()
          $value[“EnableGroupCreation”] = “false”
          $value[“GroupCreationAllowedGroupId”] = $group.ObjectId
          Set-MsolSettings -SettingId $settings.ObjectId -SettingsValue $value

          1. Thanks for posting your answer too Shaun!
            Best regards,
            Brian.

  9. Thomas says:

    Would really love to prevent everyone from creating O365 Groups (in this case through planner, which snuck up on me), but what’s the reason why I don’t have any of the “MsolSetting” cmdlets available? Just updated the WAAD module and keep getting the same, e.g.

    The term ‘Get-MsolSettingTemplate’ is not recognized as the name of a cmdlet […]

    Thanks a lot

    1. Which version of the cmdlets do you have Thomas? This needs the Preview from http://connect.microsoft.com/site1164/Downloads/DownloadDetails.aspx?DownloadID=59185 – currently 1.1.130.0. So either you don’t have that version or the module isn’t loaded in the PowerShell command window you are using.

      (Get-Module -ListAvailable | Where-Object{ $_.Name -eq ‘MSOnline’ }) | Select Version, Name, Author, PowerShellVersion | Format-List;

      should return the version you have.
      Best regards,
      Brian

      1. Thomas says:

        Thank you very much, Brian. Can’t count the number of times I went through the article to see if I might be using the wrong version of the module… and managed to miss it every single time. Naturally, all is good with the preview version.

      2. Mark says:

        Hi Brian

        I’ve got version 1.1.166.0 and I get the exact same error message. Do I have to have the specific version you mentioned? (If so, kill me now).

        1. You should be good with that version Mark – so no death penalty today. What exact error are you getting? Some of the errors in comments here are just due to using the commands on the wrong objects and some confusion between the templates and the settings object created from the template (and I’ll take the blame for confusing people).
          Best regards,

          Brian.

          1. Paul says:

            I also am getting the error: Get-MsolAllSettingTemplate : The term ‘Get-MsolAllSettingTemplate’ is not recognized as the name of a cmdlet.
            I am on version 1.1.166.0

          2. Paul says:

            I also am getting the error: The term ‘Get-MsolAllSettingTemplate’ is not recognized as the name of a cmdlet.
            I am on version 1.1.166.0

          3. Hi Paul, Mark – looks like I made a mistake with that version number. Looking at the download page it shows 2 versions – one GA and one Preview. Only the Preview version contains these cmdlets. Sorry for the confusion. I did download the newer version, but suspect as I already had the preview one loaded the preview commands were still present. http://connect.microsoft.com/site1164/Downloads/DownloadDetails.aspx?DownloadID=59185
            Sorry for the confusion here. The preview release 1.1.130.0 does contain the commands.
            Best regards,
            Brian.

  10. timothywgray says:

    Next question – Why can’t we see these groups in the mobile app? I use the Android app. Whenever I try to do this, I get a message “Unable to load groups”, or alternatively, “You’re not a member of any groups yet”. Strange.

    Again, is this supported functionality, or am I missing something?

    1. Hi Timothy, there isn’t a Planner App yet – so I assume you have the Groups App? Do you see it working with your other Groups? Sorry, I know Planner but have no experience with the Android App for Groups (apart from knowing that it has no capability to shows Planner information – other than what might be saved in the Group Files locations.
      Best regards,
      Brian.

  11. Lou Mickley says:

    Great insight Brian. what does this mean for the older Set-OwaMailboxPolicy -Identity OwaMailboxPolicy-Default -GroupCreationEnabled $false approach? Will this override that setting? Do we need both or sunset the original approach?

    1. My understanding is that you can sunset the original approach Lou. It would still block users from creating groups from ‘Groups’ if happen to be in the ‘allowed’ group but also (probably by accident) had the mailbox policy set – but they would actually bypass and create groups ok from Planner or PowerBI. Best to just have one thing controlling – as you can bet that this wouldn’t be an issue until this conversation was long forgotten.
      Best regards,
      Brian.

  12. Paul says:

    Need to know how to give other plan members the ability to add other members, presently this appears to fall to the creator of the plan!

  13. Faustina says:

    Hi Brian,

    I have selected my checklists for several to be set for preview. However, when I close the planner and open it up again, it doesn’t keep the checklists as preview for each task. How do I ensure that the checklists will always be previewed?

  14. Adam Morrison says:

    can i assign an entire group to a new Planner project without having to enter each individual/participant one by one manually?

  15. Christopher says:

    I like Planner so far. One minor, but very annoying glitch. It rearranges the order of my tasks in the buckets at random. I number each task for example: 1. Protect People, 2. Hurt People, 3. Get Money From People. 1,2,3. Easy to find. I don’t assign dates or status. Just plan tasks. Planner throughout the day rearranges them to 2,3,1 or 1,3,2 ALL DAY LONG. What gives? Please make it stop. Or all of you will fall under task number 2.

  16. Laura Napoli says:

    Entering a description on a planner task routinely overwrites the prior card you edited, not the one you are working on. This happens about 1 in 20 times for me.

    1. Thanks for the feedback Laura. Have you already opened a support incident on this behaviour?
      Best regards,
      Brian.

  17. We are a Mac org and have been user Planner for about 3 weeks now. I’ve started getting reports from a number of people (exec mgmt) who do not see the “latest version” of some tasks despite refreshing and even restarting their browsers (chrome, safari). When I check out those tasks, I see all the updates. This is usually noticed when they receive an email update from a posted comment. When the follow the link to the task, they do not see the comment or any attachments/links. The comments/attachments/links do indeed show up in the task for others (especially myself). They users complaining can also see the docs in Files directory of the Plans SITE. Any pointers or ideas on how to address this?

    1. Thanks Ayodele – I’ll check with the product group what might be happening here. It would be helpful if you or an administrator could also open a support incident via the admin portal in Office 365 as that gives us a secure channel to discuss the specific of your case. I can post back here the result of that analysis too of applicable to others.
      Best regards,
      Brian.

      1. Thanks for the response Brian.
        Will do.

  18. Manny Abubakar says:

    Hi Brian,

    Besides managing planner via the licenses SKUs what other means or methods can this feature be disabled or enabled across a large enterprise? For some reason we have planner not enabled as part of our enterprise license plans but users can go to tasks.office.com and still access it? Thoughts?

    1. Hi Manny, the only other controls are around group creation – but if you do want to use groups in other ways that may not be practical. Not sure if some block on tasks.office.com would be an option… I think the product group are considering this issue – feel free to add your thoughts on User Voice https://planner.uservoice.com/forums/330525-microsoft-planner-feedback-forum/filters/hot.
      Best regards,
      Brian.

  19. Brian Catt says:

    Hi Brian,

    I keep running into a strange situation while evaluating Planner for my organization. This occurs when I am in the plan creating tasks. I am not attempting to create or alter a task from “My tasks”.

    I create a generic task with no issues. I try to upload an image using the “upload a file” option to the task and receive an error message similar to “oops, we could not upload your file”. I will get this error until I finally delete the task and start over.

    Once I delete the original task and create a new one, I attempt to upload the image to the newly created task. Now I get an error message that reads “Upload failed. A file with that name already exists”. Even though this image is not attached to any tasks, I keep triggering this error until Planner finally gives up and says “Upload failed. Too many files are being uploaded”. That seems like an odd message since I am the only user in the organization currently using Planner.

    1. Hi Brian, it sounds like there is a problem getting the connection to the uploaded document to connect it with the task. The second message appears to indicate the upload worked – and you may be able to attach the already uploaded version – but possibly a reference to that document could not be set in the task 1st time around. If you or your O365 admin can open a support ticket for Planner we can dig in a bit deeper at the back end to understand what happened here.
      Best regards,
      Brian.

  20. Aengus says:

    Is all Planner data retained in the location/territory my SharePoint site is in, eg if my SharePoint site is located in Australia is all my planner data also located in Australia?
    Thanks

  21. Daryn Clements says:

    Are there plans to enable us to use dd/mm/yyyy as a date format?

    1. dd/mm/yyyy should work Daryn – are your regional settings all configured for that format of date? I’m working with my European colleagues this week and they confirmed this does work.
      Best regards,
      Brian.

  22. Vinny Tang says:

    Hi Brian,

    Have you seen an issue where you add a plan as a favorite, browse to say a My Tasks and then back to Planner hub the favorites are not appearing? It works for me but my manager is having this issue. Thanks!

    1. Not heard or seen that issue Vinny. How about in Outlook Web App – does it show ok there?
      Thanks,
      Brian.

      1. Vinny Tang says:

        Outlook appears to not have a Favorites Option for my manager. I can see it from my perspective.

      2. Vinny Tang says:

        Strange – I went into admin to my manager’s account removed all groups and then readded and it worked! It’s an old account from 2 yrs ago. Wonder if that caused an issue.

  23. Gareth Coulthard says:

    1) Can I give just read access to Members
    2) Can i assign multiple users to a task
    3) The date format won’t change to DD/MM/YYYY

    Thanks

    Gareth

    1. Hi Gareth – answers below:
      1. No, members cannot be read-only.
      2. We have multiple users per task on our roadmap – so hopefully in the next few months.
      3. We have heard a few reports of this – I am actually investigating for another customer right now. My European colleagues who I am working with currently have not seen this issue generally so not sure why in some cases it works and others appears to stick with MM/DD.
      I’ll add my findings…
      Best regards,
      Brian.

    2. Which language are you using Gareth. Looks like we have an issue with some date formats where we are using En-US as a fallback ‘language’ for other English variants but then this also uses the US date formats. I’m checking on our plans to correct this problem. Sorry about this.
      Best regards,
      Brian.

      1. Aengus says:

        Unfortunately Brian I don’t think your colleagues care much re the date/time format, issue has been around for months ..
        https://planner.uservoice.com/forums/330525-microsoft-planner-feedback-forum/suggestions/13688679-date-format

        1. Hopefully have an update shortly Aengus – but have to agree being English myself that having the UK (and other Englishes) fall back to the US settings seems to have been a very poor design choice.

          1. Fran Monro says:

            We are experiencing the same issue in new NZ, with the date format showing US despite regional settings being NZ English. #sadface

          2. ZB says:

            With every new version MS had a chance to give up on forcing problematic MM/DD/YY approach. They never even try. Everyone who use VBA know how is hard to match a date.
            Back to this, I’m also facing above problem. I set UK settings.
            If this info help you: This is (example of) url I get whenever I click something in the Planner: https://tasks.office.com/xxxxxxxxxxxxxx.onmicrosoft.com/en-US/Home/PlanViews/YYYYYYYYYYYYY

            You can see en-US in the url. If you delete it from the url it will still work. However, if you click something else it will come back so it override any settings that you have.
            In Board if you add new task, or edit existing, Set Due Date calendar pop up with first day Sunday. Since it changed to Monday in mine settings and this is only place it appear this way then it must be with a Planner. If your European colleagues claim it’s working then they must be looking somewhere else.
            Here is prtscr of both: Planner (left) and Outlook mail (Right) so you can compare: https://s15.postimg.org/jj1k4usaj/Untitled2.jpg

          3. This only works in parts of Europe that aren’t UK ZB – due to a bad design choice – what more can I say… It is being worked on.

          4. ZB says:

            Thank you for fast answer. Great news that it’s been working on the problem. I understand that Planner is new(er) and bugs are expected but for me it looks it’s a problem on conceptual level (just see how clumsy is that for date format example is set to choose 01/09 or 09/01 format instead of day greater than 12, which is intuitive like 25/09 or 09/25 🙂 ) . What if I would like to use US English AND dd.mm.yyyy format? At this point those things are not optional. What if someone from US want to use this where additionally his PC regional settings override Office settings? I guess there is no way to choose. Maybe for him won’t be problem to give up on these settings. But for rest of us it’s a must. Think about how confusing is that due date for some critical task is 02.03.2017. For different people it’s a month difference. And you don’t have clear control over it 🙁
            Hope that will be fixed soon but I’m skeptic because FWICS it’s fixing particular problem and not the cause.

  24. Rachel says:

    Is there any way of using Planner with out Office 365? We have office 2016 Professional.

    1. Sorry Rachel, there isn’t. It only comes as part of an Office 365 subscription.
      Best regards,
      Brian.

  25. RickiTickiToc says:

    I’ve already put this on the User Voice – But, I’ll post it up here too. Planner needs – REQUIRES the ability to use across domains. My company has a bunch of sister companies all with o365 subscriptions. We would use this tool ALOT if it worked across different domains.

Skip to main content