18 votesthinking about it · AdminSharePoint Experiences Team (email@example.com, Microsoft SharePoint) responded
Thank you for your feedback! We don’t support prefix search. There are upsides and downsides with doing suffix search by default. It’s a question of what’s best for most people. We’re taking your feedback into consideration.
Agreed. This is especially true when using document or standards numbers and a standard named E101 is not found when someone searches 101. Users expect that to work, and it should.
301 votes15 comments · SharePoint Administration » SharePoint PowerShell · Flag idea as inappropriate… · Admin →
Agree with Sean and Greg. Some compliance and retention policies prohibit these sites from viability; due to the self-service nature of *how* they are created.
I believe PnP can apply these to an existing site; but if the create site option is (rightfully) disabled; you can't get started.
63 votesin the plans · AdminSharePoint Experiences Team (firstname.lastname@example.org, Microsoft SharePoint) responded
We are planning to provide a path selection mechanism in the new admin center, but until then we’ll look to at least amend the PowerShell (note that you can already set the path using PnP PowerShell – specifically, the New-PnPTenantSite cmdlet).
I would also offer that it would be helpful to be able to create managed Communication Sites or Team/Group sites through the SharePoint Online Admin Center. We us PnP heavily and giving the Partner Pack or admins the ability to create these sites in a governed intake manner would be helpful.
869 votesworking on it · AdminSharePoint Experiences Team (email@example.com, Microsoft SharePoint) responded
This was just demoed at Ignite 2018 session BRK2136. Read more about it : https://techcommunity.microsoft.com/t5/Microsoft-SharePoint-Blog/Build-your-modern-intranet-with-SharePoint-in-Office-365-Ignite/ba-p/255453