Closed mickhowarth closed 3 years ago
@mickhowarth Thanks for your feedback! We will investigate and update as appropriate.
@mickhowarth Thank you for your time and patience throughout this issue!
Any additional information would be greatly appreciated!
If you have any other questions, please let me know. Thank you for your time and patience throughout this issue.
Thank you @JamesTran-MSFT I eventually had Office365 support call and guide me through the steps so the issue is now fixed.
I did try to fix myself, but unfortunately the documentation was difficult to follow with lots of assumptions about the user's level of knowledge in Powershell and few links to direct to explain the basic functionality - how to even launch it?! I know this is admin documentation, but my level of 365 Admin has only ever lived inside the Admin panel on the website.
Running the automated Security Defaults script within the admin panel really messed up my user's access to Exchange and the fix really wasn't easy. The Support guy who shared my screen as he was talking me through the process also ran into several command line errors whilst assisting.
To keep this OT for this page, there is a link in this document which links to a page ref Skype for Business Online Powershell Module.
Check to see if your directory already supports modern authentication by running Get-CsOAuthConfiguration from the Skype for Business Online PowerShell module.
On following this, the next page tells you that Skype for Business Powershell Module is now part of the Teams Powershell public release.
The link should probably link to the latest document in that case: https://docs.microsoft.com/en-us/microsoftteams/teams-powershell-install
As a further aside there's lots of instances where after brushing up on the basics of Powershell and trying to follow the copy/pasted command instructions in the help pages, I was met with nothing but errors - as mentioned this was the same for the MS support guy who called me and talked me through it. I'd love to be able to tell you what they were, but there were so many, I didn't keep track of them.
Frustration was getting the better of me yesterday and having bounced around and followed multiple documentation threads to no avail, I think this one was the one I commented on.
I hope this helps in some way, I know a lot of it is non specific to this page, but in general, my experince of trying to fix my issue using the support pages was really bad.
Too many assumptions are made here as to the user's knowledge of powershell, what it is, where and how to install it etc etc.
I've simply enabled Security Defaults and locked out all of my users from Exchange and need to fix this. Surely this should be something that should be easier to fix?!
I'm now in an absolute rabbit warren of tech documents regarding setting up legacy defaults via powershell, yet there's nowhere in this tangle of web pages that describes how to even install powershell, only a link to a github repo.
Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.