This is also true for configuring videoconf rooms in Teams. You have to set a magic flag via PowerShell. The whole Microsoft 365 environment smells like bit rot.
In case someone lands here due to search (and regardless of whether the problem can be solved without PowerShell) I’d like to point out that you can run PS commands on the Azure Cloud Shell (which is what I do whenever I need to use PS to automate anything and I don’t have a Windows machine).
This is available for any kind of Azure subscription (including the free tier), and although it may require installing extra modules in that environment, it always works since the PS context is running inside a Windows container.
I just encountered this setting up my personal domain email.
It’s super annoying to get the powershell exchange online plugin working on an M1 Mac. The documentation says to use homebrew, but to work around the M1 issue you have to then download a specific package from Mac Ports and manually symlink some libraries.
It was really a poor impression to realise it’s so much harder to set up on anything but a windows machine.
This seems like more of a documentation problem from a technical problem... from the issue discussion we can see that it is indeed possible to do this without PowerShell, but I agree that the doc the MSFT employee linked to does not make it very clear how. Hopefully MS provides a step-by-step for this, or adds the automatic record generation to the web interface.
This isn’t actually true its just not well documented in the documentation it implies you need power shell then the actual instructions for doing it in the azure console are just lower on the page
So it’s essentially not possible without a Windows machine? Seems like a strange restriction especially if this capability existed before and was taken away. Especially if the IT team command and control is Linux which is likely
Not so likely because if you have O365, you most likely also have windows computers in your env. It is very, very unlikely to solely be running an OSX/NIX env and use O365 beause the mdm, intune, autopilot, Windows 10, Access Desktop app and such are Windows only.
And excel on OSX sucks.
And there are no desktop office apps for linux. Web apps work though. Good luck with power pivot and complicated tasks though.
Not all O365 licenses come with Powershell access. And yes, I'd rather click, CLI commands are not discoverable unless you happen to find a mention of the commands in the documentation.
Not true at all, every user account, even unlicensed, as long as it is assigned an UPN, or has an AD object has Powershell access.
CLi commands are very discoverable via Powershell/Powershell ISE and Cloud Powershell which is available in any azure instance or logging in the O365 admin portal.
Yes, really. You can have unlicensed accounts on Cloud only O365, or hybrid o365. You can auth, you can SMTP auth (called basic auth), you can do modern auth, you can do API secret auth, etc.
Are you positive? Even with one of the most basic $4 Exchange P1 licenses I was able to do any powershell administration I desired. Setup DKIM and DMARC without issues. The only cheaper license is a $2 kiosk license
An admin account does not need a license, the license is the entitlement for that service. The OP in this thread does not know O365 administration - you are correct, you can use powershell on any license, and if you do not have a license at all.
