Anonymous
My feedback
-
73 votes
An error occurred while saving the comment -
1 vote
An error occurred while saving the comment Anonymous
commented
Sounds like an issue with bad session data. We use OKTA for federation and see similar once in a blue moon first thing to do is a user restart assuming that does work.. which it most likely won't. Kill all session data via SharePoint online powershell or via the GUI goto the user profile I think it shows under OneDrive. It's part of the SharePoint online module but will kill all sessions it usually takes around 30 mins but will solve the issue.
-
11,024 votes
This feature remains on the backlog. We will update you when we have status changes to share.
Anonymous
supported this idea
·
-
513 votes
This feature request is still be reviewed by the feature team. No additional details are available at this time.
-Warren
An error occurred while saving the comment Anonymous
commented
Please this is another one that needed
-
640 votes
An error occurred while saving the comment Anonymous
commented
Super important issue as if we want to use Teams for alert messages than this needs to be in place
-
7,088 votes
Due to prioritization of other work-items this has been moved to the backlog. We will update when it is being actively worked on again.
Thanks.
An error occurred while saving the comment Anonymous
commented
Technically we need this as the admins cant manage notification settings so we need to let them know they must set it for certain channels
-
256 votes
An error occurred while saving the comment Anonymous
commented
This is the second or third issue I have seen around this type of issue I think this should have been looked at a long time ago. Teams meeting security is currently very lacking compared to other apps. I raised tickets with MS over this and just got a generic this is a development issue post in User voice response which is awful as its a real security problem to ensure that only the people that should be in the meeting are.
Anonymous
supported this idea
·
An error occurred while saving the comment Anonymous
commented
This shouldn't be a suggestion as its a major security risk. See all the stuff happening with Zoom right now this is the kind of thing that causes it.
-
19 votesAnonymous
supported this idea
·
An error occurred while saving the comment Anonymous
commented
This is a major issue, had a non internal user ***** the link for a re-occurring meeting the link is based on the name which means even if you rebuild the meeting with the same name they can join. I mentioned this to support and they said whilst its a security issue it had to go here to probably not be looked a for 5 years. So effectively we were Teams bombed a MS's response to this is to ignore the issue.I have since gone back to our staff and trained them around this new form of information phishing but as an administrator I hate leaving things to chance.
-
648 votesAnonymous
supported this idea
·
-
2 votesAnonymous
shared this idea
·
They have this your MS admin can set it on or you can do it in meeting settings after the meeting is created. What they really need is password protection on the meetings