I am not sure if this is an edge case…. I’d love to know how others work.
On some calls – for example a managers meeting – you want to temporarily add in someone just for a quick question. You don’t want them to remain after the call. It is kind of a security or privacy issue if you don’t remove them.
So I find it really annoying when I forgot to remove them after the call and they probably find it annoying when they get our messages after the call. So I would prefer not to have to remove the person manually.
Suggestion – next to “Add people”, I think it would be really cool to add a person via an option “Add people (temporarily)”.
In the SharePoint App, the Find page shows frequent sites and people, which is super useful for quickly getting to sites or people your often interact with. The same Frequent sites functionality can be used in other places in SharePoint with the Sites web part.
It would be great if there was also a Popular Sites section, and even a Popular People section (though that name might need some workshopping!). This would make it easier for users to find important sites quickly, even if they don’t access them often. It would be especially useful for new users.
With this addition, the existing sections may need to be renamed to be clearer, e.g. Frequent Sites would become My Frequent Sites.
We all love Microsoft Teams and I think this UI looks like it is about to be clever, but it is not.
When starting a new chat… If I pick 1 person… please attempt to guess the 2nd person I will add to the chat. People are often related and I know it would be a nice for all Microsoft Teams users if the people picker showed the like people that I will chat with together.
Today, it doesn’t matter who I pick first in the chat, the search always shows the same people.
Please pick who I will probably pick next … it should change the people based on who I am adding.
More info: Delve tells me who I talk to a bit, that would be ok. But when you talk to a manager, you probably are going to pick another manager. When I talk to an Azure DevOps engineer, I am probably going to pick another Azure engineer (not a React developer).
Your Azure credentials have not been set up or have expired,
1955 | please run Connect-AzAccount to set up your Azure credentials.
1956 | ClientAssertionCredential authentication failed: A
1957 | configuration issue is preventing authentication - check the
1958 | error message from the server for details. You can modify the
1959 | configuration in the application registration portal. See
1960 | https://aka.ms/msal-net-invalid-client for details. Original
1961 | exception: AADSTS700024: Client assertion is not within its
1962 | valid time range. Current time: 2022-10-20T07:47:12.7446078Z,
1963 | assertion valid from 2022-10-20T07:37:08.0000000Z, expiry time
1964 | of assertion 2022-10-20T07:42:08.0000000Z. Review the
1965 | documentation at
❌ Bad example – Error on deployment – assertion valid from 2022-10-20 07:37 to 2022-10-20 07:42 🔥(5 minutes)