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.
Figure: Plain menu without icon/emojis is not very welcoming
Figure: Emojis make it a bit nicer in some cases. In this case they are the wrong UI… I want to emphasize the fact that these are links to Teams (rather than SharePoint) being https://teams.microsoft.com/l/team/xxxxx
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.
✅ Figure: Good example – Add a custom image in the Quick Links web part is easy
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:
Figure: Each item links to a different portal, i.e. https://sswcom.sharepoint.com/sites/XXX
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
Figure: URL being randomly rewritten to the “full” form (i.e. full page’s path)
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:
Figure: Weird “sw=auth” querystring parameter
Can you please explain what is causing the issue?
How do we fix it? We want to be using the “short” form as much as possible
Hey Teams / SharePoint Team Product Owner,
I don’t think this UI is clear to users. I just did a quick poll and people that use this UI did not know about the 3 dots “…” (see red arrow)
Please change to a 3
rd button that says “Manage” or “Manage Access”
Figure: Bad UX – Who clicks these 3 dots?
It then brings open this …
Figure: Use the Share | Shared with | Manage access… – then users can get the correct link to give users
Say you add user to a group… you should be able to see this change in the Azure AD Audit logs.
Figure: New user added to a distribution group
The Audit log details work great for users. For example, when you make a change to a user in AD and sync with Azure AD (using AAD Connect), you get great visibility of what was changed.
✅ Figure: Good example: Azure AD | [user] | Audit logs | Audit Log Details with Old Value & New Value
Sadly you can’t see who changed it.
When you make a change to a distribution group in AD (e.g. add a new member) and sync, there are no details at all
❌ Figure: Bad example – Azure AD | [group] | Audit logs | Audit Log Details shows no details (you can’t see that a new user was added to the distribution group)
Suggestion: Please add the details of who changed what for both users and distribution groups in the Audit logs.
When filling in a form the user icon (aka Account Name) on the top right is missing.
It would be awesome if the Forms questionnaire showed who was signed in. They could copy the Forms responses which is really clear. So it would be awesome if they had the same green bar below:
✅ Figure: Good example – In the green bar I can see who is signed in being “PW”
❌ Figure: Bad example – How the forms currently look – there is no indication who is signed in
There is inconsistency in the Person menus…
✅ Figure: Good example – Power BI shows my “License type:” is Pro
❌ Figure: Bad example – Office 365 does not tell me what license I have
❌ Figure: Bad example – Dynamics 365 does not tell me what license I have More Info:
In this case the
Office | Person menu should show ”Microsoft 365 E3”
And link off to
Figure: My Account shows the licenses you own
Teams search is super important, and I hope this one is on Microsoft’s backlog.
I expect Teams search and SharePoint search to have consistent results. Do others?
Not finding stuff you have permissions too is super frustrating. So this one has always confused me…. Do you consider it a bug?
Watch this one:
Figure: Teams and SharePoint Search Bug with Jean Thirion – YouTube (5 mins)
I think Jean did a great explanation of the permissions problem.
This is really weird behaviour – fire up Fiddler and you can see what Teams is doing in the background.
Turns out that when you
search in Teams before it shows you what you have access to, it weirdly adds a refining query to only show documents from a list of every group you are a member of…
Figure: This string of group id’s is about 75 items long, and I believe it is made up of every Team I am a member of… I’d like to turn this off
Figure: Query yields 1 result
When I remove that refining query, it works as expected:
Figure: In Fiddler when you edit the request and remove the group id refining query …it yielded 21 results
So I would say this appears to be a deliberate decision rather than a bug, though I think it is important to be able to turn it off if you want to find stuff using Team’s search 😂
In fact I would turn it off by default, so it is consistent with SharePoint Search
See the below text from our document on how to set up the security ourselves
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.
Figure: SharePoint Advanced Permission setup – 3 traditional SharePoint Groups
Figure: “Members” SharePoint group has exactly one member – the Office 365 Group
Figure: “Owners” SharePoint group is Empty!
(Note for SharePoint gurus: O365-xxx-Members is mapped to SharePoint-xxx-members, but O365-xxx-Owners is mapped to… Site Collection Administrators! Crazy.)
Figure: “Site Collection Administrators” are mapped to The Site Owners Office 365 Group
SharePoint membership grants access to SharePoint resources, while access to Teams features (Channels, tabs, apps) is controlled directly via
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.
Dear Microsoft Forms Product Owner,
When looking at the feedback from my forms surveys, I prefer Bar Charts over Pies. Does anyone like Pies? – I find them less readable.
Suggestion: I would like to go to Tools | Options and set my preference
Question: I think I have noticed that Forms show Bars when there are 6 or more options. Right? If so, I guess I should always make sure I have 6 options 😊 😊
Figure: Pie chart
Figure: Bar chart
That is an odd decision. I was just talking to a person form New Zealand who said:
“we actually have a rule to never use a pie chart :) The only time they’re somewhat useful is if you are comparing 2 things. Anything more and it’s not really readable”
Please fix it or give us an option to allow us to fix it.
Add a trigger in Power Automate when a Team’s name has changed.
E.g. I want to create a Flow to send a email notification to the manager when a Team’s name has changed.
Figure: Suggestion – This Power Automate cloud flow creation dialog is missing a tigger to inform us when a Team name has changed