%3CLINGO-SUB%20id%3D%22lingo-sub-1403622%22%20slang%3D%22en-US%22%3ERe%3A%20Sync%20message%20center%20posts%20to%20Microsoft%20Planner%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1403622%22%20slang%3D%22en-US%22%3E%3CP%3EThat's%20interesting%20and%20a%20good%20start.%20Probably%20will%20need%20some%20improvements%20to%20get%20really%20useful.%20That%20part%20with%20duplicate%20tasks%20sounds%20a%20bit%20clunky.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1403994%22%20slang%3D%22en-US%22%3ERe%3A%20Sync%20message%20center%20posts%20to%20Microsoft%20Planner%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1403994%22%20slang%3D%22en-US%22%3E%3CP%3EThanks%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F33735%22%20target%3D%22_blank%22%3E%40Oleg%20K%3C%2FA%3E%26nbsp%3B.%20We%20would%20love%20your%20feedback%20on%20how%20would%20you%20like%20Message%20updates%20to%20be%20handled.%26nbsp%3B%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1403447%22%20slang%3D%22en-US%22%3ESync%20Message%20Center%20posts%20to%20Microsoft%20Planner%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1403447%22%20slang%3D%22en-US%22%3E%3CP%3EThe%20%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fmicrosoft-365%2Fadmin%2Fmanage%2Fmessage-center%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3EMessage%20center%3C%2FA%3E%20in%20the%20%3CA%20href%3D%22https%3A%2F%2Fgo.microsoft.com%2Ffwlink%2Fp%2F%3Flinkid%3D2070717%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3EMicrosoft%20365%20admin%20center%3C%2FA%3E%20is%20designed%20to%20help%20you%20keep%20track%20of%20upcoming%20changes%20to%20Microsoft%20365%2C%20including%20new%20and%20changed%20features%2C%20planned%20maintenance%2C%20and%20other%20important%20announcements.%20It%E2%80%99s%20where%20we%20post%20official%20announcements%20to%20help%20you%20take%20a%20proactive%20approach%20to%20change%20management.%20Each%20post%20provides%20you%20with%20a%20high-level%20overview%20of%20planned%20changes%20along%20with%20links%20to%20detailed%20information%20to%20help%20you%20prepare%20for%20and%20manage%20the%20change.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3ETo%20help%20you%20navigate%20the%20myriad%20of%20information%20that%20arrives%20in%20the%20Message%20center%2C%20and%20more%20importantly%2C%20to%20help%20you%20decide%20whether%20or%20not%20to%20act%20on%20the%20information%2C%20we%20are%20introducing%20the%20ability%20to%20sync%20your%20message%20center%20to%20Microsoft%20Planner.%20This%20feature%20will%20be%20entering%20Targeted%20Release%20in%20mid-May%202020%20and%20released%20to%20General%20Availability%20this%20summer%20and%20it%20will%20include%20the%20ability%20to%20choose%20which%20type%20of%20messages%20are%20sync%E2%80%99d%20and%20to%20sync%20messages%20on%20a%20set%20cadence.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-center%22%20image-alt%3D%22MCSync1.jpg%22%20style%3D%22width%3A%20803px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F193135i93D31396628131C9%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20title%3D%22MCSync1.jpg%22%20alt%3D%22Planner%20integration%20for%20message%20center%20posts%22%20%2F%3E%3CSPAN%20class%3D%22lia-inline-image-caption%22%20onclick%3D%22event.preventDefault()%3B%22%3EPlanner%20integration%20for%20message%20center%20posts%3C%2FSPAN%3E%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EOnce%20a%20message%20has%20been%20sync%E2%80%99d%20to%20Planner%2C%20it%20will%20show%20up%20in%20Planner%20as%20a%20task.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-center%22%20image-alt%3D%22MCSync2.jpg%22%20style%3D%22width%3A%20999px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F193139iAF5ADDABDB38D922%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20title%3D%22MCSync2.jpg%22%20alt%3D%22Planner%20with%20sync'd%20message%20center%20posts%22%20%2F%3E%3CSPAN%20class%3D%22lia-inline-image-caption%22%20onclick%3D%22event.preventDefault()%3B%22%3EPlanner%20with%20sync'd%20message%20center%20posts%3C%2FSPAN%3E%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EAs%20illustrated%20above%2C%20all%20Message%20center%20post%20titles%20will%20be%20prefixed%20with%20the%20associated%20service%20in%20brackets%20(e.g.%2C%20%5BSharePoint%5D.%20When%20a%20Message%20center%20post%20is%20updated%2C%20the%20sync%20process%20will%20add%20a%20new%20task%20to%20Planner%3B%20thus%2C%20you%20could%20have%20multiple%20tasks%20associated%20with%20one%20post.%20To%20distinguish%20the%20update%2C%20the%20updated%20Message%20center%20post%20title%20will%20be%20prefixed%20with%20(Update).%20For%20example%2C%20%3CSTRONG%3E(Update)%20%5BSharePoint%5D%3C%2FSTRONG%3E.%20For%20each%20task%20that%20is%20created%2C%20the%20Start%20Date%20will%20be%20set%20to%20when%20the%20task%20was%20created%2C%20and%20the%20Message%20center%20post%20publication%20date%20is%20captured%20in%20the%20Notes%20field.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3ECheck%20out%20the%20new%20integration%20and%20let%20us%20know%20what%20you%20think!%26nbsp%3B%20We%E2%80%99d%20love%20to%20get%20your%20feedback!%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E--The%20Microsoft%20365%20Release%20and%20Delivery%20Experience%20(RDX)%20team%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-TEASER%20id%3D%22lingo-teaser-1403447%22%20slang%3D%22en-US%22%3E%3CP%3ETo%20help%20you%20navigate%20the%20myriad%20of%20information%20that%20arrives%20in%20message%20center%2C%20and%20more%20importantly%2C%20to%20help%20you%20decide%20whether%20or%20not%20to%20act%20on%20the%20information%2C%20we%20are%20introducing%20the%20ability%20to%20sync%20your%20message%20center%20to%20Microsoft%20Planner.%3C%2FP%3E%3C%2FLINGO-TEASER%3E%3CLINGO-LABS%20id%3D%22lingo-labs-1403447%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EAdmin%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EMessage%20Center%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EPlanner%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1404483%22%20slang%3D%22en-US%22%3ERe%3A%20Sync%20Message%20Center%20posts%20to%20Microsoft%20Planner%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1404483%22%20slang%3D%22en-US%22%3E%3CP%3EI%20know%20that%20this%20is%20not%20realistic%2C%20but%20with%20this%20sync%20and%20messages%20coming%20all%20the%20time%20it%20would%20make%20this%20plan%2Fproject%20never%20ending%20and%20constantly%20growing.%20Maybe%20it%20would%20be%20beneficial%20to%20split%20it%20in%20multiple%20plans%20based%20on%20feature%2Fchange%20final%20release%20date.%20But%20this%20is%20problematic%20as%20MS%20changes%20dates%20a%20lot%20(postpones%2C%20etc.).%20This%20way%20you%20would%20be%20able%20to%20eventually%20close%20the%20plan%2C%20once%20all%20features%20in%20that%20time%20segment%20are%20been%20taken%20care%20of.%20Again%20maybe%20harder%20to%20implement%2C%20but%20it%20would%20be%20better%20if%20planner%20could%20update%20the%20current%20task%20instead%20of%20creating%20a%20duplicate%20with%20an%20updated%20name.%20Because%20you%20would%20also%20have%20to%20move%20all%20the%20notes%2C%20comments%20and%20steps%20to%20the%20new%20one%20manually.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1407568%22%20slang%3D%22en-US%22%3ERe%3A%20Sync%20Message%20Center%20posts%20to%20Microsoft%20Planner%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1407568%22%20slang%3D%22en-US%22%3E%3CP%3EI%20like%20this%20idea%20a%20lot%20and%20am%20very%20excited%20to%20see%20it%20in%20action.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1429414%22%20slang%3D%22en-US%22%3ERe%3A%20Sync%20Message%20Center%20posts%20to%20Microsoft%20Planner%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1429414%22%20slang%3D%22en-US%22%3E%3CP%3EGood%20initiative.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1486103%22%20slang%3D%22en-US%22%3ERe%3A%20Sync%20Message%20Center%20posts%20to%20Microsoft%20Planner%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1486103%22%20slang%3D%22en-US%22%3E%3CP%3EAny%20update%20on%20this%3F%20It%20looks%20the%20feature%20is%20not%20available%20yet%20in%20targeted%20release.%20Really%20looking%20forward%20to%20this%20one!%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E
Microsoft

The Message center in the Microsoft 365 admin center is designed to help you keep track of upcoming changes to Microsoft 365, including new and changed features, planned maintenance, and other important announcements. It’s where we post official announcements to help you take a proactive approach to change management. Each post provides you with a high-level overview of planned changes along with links to detailed information to help you prepare for and manage the change.

 

To help you navigate the myriad of information that arrives in the Message center, and more importantly, to help you decide whether or not to act on the information, we are introducing the ability to sync your message center to Microsoft Planner. This feature will be entering Targeted Release in mid-May 2020 and released to General Availability this summer and it will include the ability to choose which type of messages are sync’d and to sync messages on a set cadence.

 

Planner integration for message center postsPlanner integration for message center posts

 

Once a message has been sync’d to Planner, it will show up in Planner as a task.

 

Planner with sync'd message center postsPlanner with sync'd message center posts

 

As illustrated above, all Message center post titles will be prefixed with the associated service in brackets (e.g., [SharePoint]. When a Message center post is updated, the sync process will add a new task to Planner; thus, you could have multiple tasks associated with one post. To distinguish the update, the updated Message center post title will be prefixed with (Update). For example, (Update) [SharePoint]. For each task that is created, the Start Date will be set to when the task was created, and the Message center post publication date is captured in the Notes field.

 

Check out the new integration and let us know what you think!  We’d love to get your feedback!

 

--The Microsoft 365 Release and Delivery Experience (RDX) team

6 Comments
Super Contributor

That's interesting and a good start. Probably will need some improvements to get really useful. That part with duplicate tasks sounds a bit clunky.

Microsoft

Thanks @Oleg K . We would love your feedback on how would you like Message updates to be handled.  

Super Contributor

I know that this is not realistic, but with this sync and messages coming all the time it would make this plan/project never ending and constantly growing. Maybe it would be beneficial to split it in multiple plans based on feature/change final release date. But this is problematic as MS changes dates a lot (postpones, etc.). This way you would be able to eventually close the plan, once all features in that time segment are been taken care of. Again maybe harder to implement, but it would be better if planner could update the current task instead of creating a duplicate with an updated name. Because you would also have to move all the notes, comments and steps to the new one manually.

Valued Contributor

I like this idea a lot and am very excited to see it in action.

Senior Member

Good initiative.

Any update on this? It looks the feature is not available yet in targeted release. Really looking forward to this one!