For our customers we get their SharePoint site pointing to Teams and vice versa… I believe it is the right thing to do but the right emoji would cause this to be more UI obvious ✨

In SharePoint there is an issue with menu customization that blocks good UX. E.g. I want to have links to both the SharePoint portals and the right Teams in the menu.

Ideally we should be able to use SharePoint and Teams official icons, i.e.:

But there doesn’t seem to be any supported way to do so! 

I assume it is a bad idea to inject HTML via a custom SPFX solution or some nasty CSS… It is better to stay within the framework and have easy upgrade.

In summary I am saying that emojis do not do the job every time (BTW I do love emojis). This is one example where emojis are not as good as images.

SharePoint is important to us. It is the intranet of almost all SSW’s clients. I am suggesting that SharePoint should not be making the job of putting images in a menu, hard. It should be simple. 

The goal should be to make it the same as other webparts. I’m thinking of the ‘Quick Links’ Web Part.  Please allow us to add a custom image or an icon to all of our menu items.

I think URLs matter and I prefer neat ones.

I’m experiencing a weird bug on our Intranet and cannot figure out why this is happening.

Everytime I click on one of the menu items the URL shows slightly differently.

We have several portals (Team Sites) linked from our Hub Navigation:

Every single link is setup using the short URL form – i.e. not linking directly to the aspx page.

However, sometimes/often/randomly, when clicking one of the menu items, the URL is somehow rewritten to https://sswcom.sharepoint.com/sites/XXX/SitePages/Home.aspx

Moreover, clicking the Site’s “home” tile (i.e. Site Logo) will almost always toggle – yes toggle – between the two URLs… 

I have noticed that, before it flicks to the “long” form, there is a weird querystring parameter being added for a split second, and then the rewrite happens:

1. Can you please explain what is causing the issue?

2. How do we fix it? 
   We want to be using the “short” form as much as possible

See the below text from our document on how to set up the security ourselves

Context 

Whenever you create a Site Collection, two O365 groups get created (xxx-Owners and xxx-Members). For retro-compatibility, these O365 groups are automatically added to the SharePoint groups at creation time.  

(Note for SharePoint gurus: O365-xxx-Members is mapped to SharePoint-xxx-members, but O365-xxx-Owners is mapped to… Site Collection Administrators! Crazy.) 

SharePoint membership grants access to SharePoint resources, while access to Teams features (Channels, tabs, apps) is controlled directly via O365 groups.  

Problem 

The problem with this model is we cannot add AD (Active Directory) groups (or even O365 groups) within O365 groups (no nesting allowed). So, if we want to give access to two different sites to the same people (say SSWDevelopers), we must add ALL MEMBERS manually on EACH generated O365 group. That is ridiculous, and hard to maintain long term. 

From the audit result, if you double-click a line and then click “More information”, here is what you see :

Which is great! A lot of useful information in there!

However, if you export the Audit result, here is what you get :

The whole “More information” data is a single column !!

It is indeed easy to format but requires extra work, and is not ideal.

Suggestion: make these information extra columns in the export!

Consider this search result:

When I click on “Details” (or double click), I can see :

This is terribly misleading ! The source is displayed as “/Shared Documents/xxx”, which I assumed being “sswcom.sharepoint.com/Shared Documents/xxx”, but is in fact “sswcom.sharepoint.com/sites/SSWNetworkAdmins/Shared Documents/xxx”. The displayed path is indeed relative, but relative to the site collection, not the whole tenant. Which is misleading in a “unified” log (where results can come from pretty much any site collection).

Suggestion: I would love to have options to:

1. See the source Site Collection
2. Filter down & sort by Site Collection

Office 365 dates seem to be too simple. Audit data should be crystal clear (as detailed as possible).

I find audit history on Office365 to be lacking E.g. sswcom.sharepoint.com

It certainly is less useful than Sharepoint 2016 as dates were shown better.

I searched for a record on the 2 lists and here is what I see:

Office 365
Eg. sswcom.sharepoint.com show me last activity as Friday at 2:15 PM

SharePoint 2016
Eg. intranet.ssw.com.au show me last activity as Created at 9/03/2018 5:06 PM

I find it less useful as it doesn’t tell me the date it was created on. I would prefer to have something like “2 days ago at 2:15 PM (Friday 9/03/2018)”

PS: This is very simple to do with Moment.js

1. In o365, click New and users get 3 options. Which option should I use?
2. I think you’ll say the 3rd one. The new one. I think Microsoft should bold the 3rd one and move it to the top. Right?
3. Are the first 2 basically the same, with the 2nd one giving more extensibility?
4. Do you think those first 2 legacy choices should be combined?
5. If not I’d change the name of the 2nd option from “Web Part Page” to “Wiki Page with Layout options”
6. Do you think the 3rd option “Site Page” should be renamed to “Modern Page”
7. In general marketing terms I think “web part” is dated and they have a bad history – call the new ones “widgets” please

[Also posted at https://sharepoint.uservoice.com/forums/330318-sharepoint-administration/suggestions/19505032-help-me-create-a-new-page]