SOLVED

Official megamenu reference

%3CLINGO-SUB%20id%3D%22lingo-sub-299796%22%20slang%3D%22en-US%22%3EOfficial%20megamenu%20reference%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-299796%22%20slang%3D%22en-US%22%3E%3CP%3EAccording%20to%20the%20Microsoft%20365%20roadmap%2C%20the%20megamenu%20was%20released%20in%20November%202018.%26nbsp%3BUnfortunately%2C%20I%20can't%20find%20any%20trace%20of%20it%20in%20the%20settings%20or%20in%20the%20Microsoft%20documentation.%20Any%20pointers%20to%20an%20official%20reference%20would%20be%20appreciated.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-299796%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EMegamenu%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3ENavigation%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-333113%22%20slang%3D%22en-US%22%3ERe%3A%20Official%20megamenu%20reference%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-333113%22%20slang%3D%22en-US%22%3E%3CP%3EOfficial%20blog%20post%20about%20Megamenus%3C%2FP%3E%0A%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2FMicrosoft-SharePoint-Blog%2FOrganize-your-SharePoint-sites-with-megamenu-navigation-and-new%2Fba-p%2F328068%22%20target%3D%22_blank%22%3Ehttps%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2FMicrosoft-SharePoint-Blog%2FOrganize-your-SharePoint-sites-with-megamenu-navigation-and-new%2Fba-p%2F328068%3C%2FA%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-332069%22%20slang%3D%22en-US%22%3ERe%3A%20Official%20megamenu%20reference%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-332069%22%20slang%3D%22en-US%22%3E%3CP%3EThe%20megamenu%20is%20currently%20being%20rolled%20out.%20I%20got%20it%20on%20a%20targeted%20release%20tenant%2C%20and%20it%20should%20be%20deployed%20to%20all%20Office%20365%20customers%20by%20the%20end%20of%20March.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-320828%22%20slang%3D%22en-US%22%3ERe%3A%20Official%20megamenu%20reference%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-320828%22%20slang%3D%22en-US%22%3E%3CP%3EAny%20update%20when%20MegaMenus%20will%20be%20released%20in%20the%20US%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-300955%22%20slang%3D%22en-US%22%3ERe%3A%20Official%20megamenu%20reference%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-300955%22%20slang%3D%22en-US%22%3E%3CP%3EI%20got%20an%20%3CA%20href%3D%22https%3A%2F%2Ftwitter.com%2Fmkashman%2Fstatus%2F1072933835027828737%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Eanswer%20from%20Mark%20Kashman%3C%2FA%3E%20via%20twitter%3A%20The%20roadmap%20info%20was%20a%20mishap%20and%20the%20megamenu%20rollout%20is%20expected%20in%20December.%3C%2FP%3E%3CBLOCKQUOTE%3E%3CHR%20%2F%3E%3C%2FBLOCKQUOTE%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-300366%22%20slang%3D%22en-US%22%3ERe%3A%20Official%20megamenu%20reference%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-300366%22%20slang%3D%22en-US%22%3E%3CP%3EI%20wholeheartedly%20agree%20with%20you%20Christophe%20regarding%20the%20lack%20of%20documentation.%20It%20feels%20like%20the%20recent%20major%20SharePoint%20release%20announcements%20in%20the%20Message%20Center%20is%20missing%20detailed%20documentation%20regarding%20the%20change.%20The%20%22Additional%20information%22%20link%20now%20often%20refers%20back%20to%20old%20blog%20posts%20from%20Ignite%20that%20is%20missing%20the%20detailed%20information%20I%20need%20to%20be%20able%20to%20prepare%20my%20self%20and%20my%20customers%20for%20the%20upcoming%20change.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-299863%22%20slang%3D%22en-US%22%3ERe%3A%20Official%20megamenu%20reference%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-299863%22%20slang%3D%22en-US%22%3E%3CP%3EThanks%20for%20the%20reply%20Dan.%20That%20makes%20sense%2C%20there%20is%20clearly%20an%20inconsistency%20in%20the%20roadmap.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EStill%2C%20I%20would%20expect%20to%20find%20some%20official%20documentation%20if%20it%20is%20rolled%26nbsp%3B%20out%20this%20month.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-299827%22%20slang%3D%22en-US%22%3ERe%3A%20Official%20megamenu%20reference%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-299827%22%20slang%3D%22en-US%22%3E%3CP%3EThe%20%3CA%20href%3D%22https%3A%2F%2Fwww.microsoft.com%2Fen-us%2Fmicrosoft-365%2Froadmap%3Ffilters%3D%26amp%3Bsearchterms%3D33132%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Eroadmap%3C%2FA%3E%26nbsp%3Bitem%20is%20still%20marked%20as%20%22In%20development%22%20event%20though%20release%20date%20says%20November%202018.%20The%20%3CA%20href%3D%22https%3A%2F%2Fadmin.microsoft.com%2FAdminPortal%2Fhome%3Fswitchtomodern%3Dtrue%23%2FMessageCenter%3Fid%3DMC165552%22%20target%3D%22_self%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3EMicrosoft%20365%20Message%20Center%20message%3C%2FA%3E%20says%20the%20rollout%20should%20begin%20the%20end%20of%20November%20and%20that%20it%20should%20be%20released%20worldwide%20by%20the%20end%20of%20December.%20I%20haven't%20seen%20it%20in%20any%20of%20the%20tenants%20I%20have%20access%20to%20that%20is%20under%20Targeted%20Release%2C%20so%20I'm%20guessing%20it's%20still%20not%20fully%20released%20yet.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-698365%22%20slang%3D%22en-US%22%3ERe%3A%20Official%20megamenu%20reference%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-698365%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F29417%22%20target%3D%22_blank%22%3E%40Christophe%20Humbert%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EHi%2C%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ENow%20that%20mega%20menus%20are%20here%2C%20we%20are%20trying%20to%20deploy%20them%20across%20about%20a%20dozen%20hub%20sites.%20Each%20site%20has%20several%20sub%20sites%20and%20we%20would%20like%20to%20duplicate%20the%20menu%20structure%20across%20all%20sites.%20Does%20anyone%20have%20a%20script%20available%20that%20can%20facilitate%3F%20Is%20this%20possible%20with%20Power%20Shell%3F%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThanks%20very%20much%20for%20any%20assistance!%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-698705%22%20slang%3D%22en-US%22%3ERe%3A%20Official%20megamenu%20reference%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-698705%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F314277%22%20target%3D%22_blank%22%3E%40Ted_Ruberti%3C%2FA%3Earen't%20you%20able%20to%20use%20the%20out-of-the-box%20functionality%20for%20that%3F%20No%20need%20for%20duplication%2C%20sites%20should%20inherit%20from%20hubs%20and%20sub-sites%20should%20inherit%20from%20the%20top-level%20sites.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-699661%22%20slang%3D%22en-US%22%3ERe%3A%20Official%20megamenu%20reference%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-699661%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F29417%22%20target%3D%22_blank%22%3E%40Christophe%20Humbert%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThank%20you%20for%20the%20reply.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20need%20to%20investigate.%20My%20understanding%20was%20that%20the%20menus%20needed%20to%20be%20duplicated%20across%20the%20multiple%20hub%20sites.%20We%20are%20just%20rolling%20out%20our%20intranet%20now%2C%20and%20the%20feedback%20I%20received%20was%20that%20the%20menus%20need%20to%20be%20replicated%20across.%20I%20am%20still%20in%20the%20process%20of%20gaining%20access%20to%20the%20environment%2C%20which%20does%20not%20help.%20Apologies%20for%20that%2C%20but%20beyond%20my%20control%20right%20now!%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EOkay%2C%20I%20will%20dig%20in%20deeper.%20Thanks%20again%20for%20the%20willingness%20to%20assist!%20%3A)%3C%2Fimg%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E
Highlighted
Frequent Contributor

According to the Microsoft 365 roadmap, the megamenu was released in November 2018. Unfortunately, I can't find any trace of it in the settings or in the Microsoft documentation. Any pointers to an official reference would be appreciated.

10 Replies
Highlighted

The roadmap item is still marked as "In development" event though release date says November 2018. The Microsoft 365 Message Center message says the rollout should begin the end of November and that it should be released worldwide by the end of December. I haven't seen it in any of the tenants I have access to that is under Targeted Release, so I'm guessing it's still not fully released yet.

Highlighted

Thanks for the reply Dan. That makes sense, there is clearly an inconsistency in the roadmap.

 

Still, I would expect to find some official documentation if it is rolled  out this month.

Highlighted

I wholeheartedly agree with you Christophe regarding the lack of documentation. It feels like the recent major SharePoint release announcements in the Message Center is missing detailed documentation regarding the change. The "Additional information" link now often refers back to old blog posts from Ignite that is missing the detailed information I need to be able to prepare my self and my customers for the upcoming change. 

Highlighted

I got an answer from Mark Kashman via twitter: The roadmap info was a mishap and the megamenu rollout is expected in December.


 

Highlighted

Any update when MegaMenus will be released in the US?

Highlighted

The megamenu is currently being rolled out. I got it on a targeted release tenant, and it should be deployed to all Office 365 customers by the end of March.

Highlighted
Best Response confirmed by Kevin Crossman (MVP)

@Christophe Humbert 

 

Hi, 

 

Now that mega menus are here, we are trying to deploy them across about a dozen hub sites. Each site has several sub sites and we would like to duplicate the menu structure across all sites. Does anyone have a script available that can facilitate? Is this possible with Power Shell? 

 

Thanks very much for any assistance! 

Highlighted

@Ted_Rubertiaren't you able to use the out-of-the-box functionality for that? No need for duplication, sites should inherit from hubs and sub-sites should inherit from the top-level sites.

Highlighted

@Christophe Humbert 

 

Thank you for the reply.

 

I need to investigate. My understanding was that the menus needed to be duplicated across the multiple hub sites. We are just rolling out our intranet now, and the feedback I received was that the menus need to be replicated across. I am still in the process of gaining access to the environment, which does not help. Apologies for that, but beyond my control right now! 

 

Okay, I will dig in deeper. Thanks again for the willingness to assist! :)