You cannot setup DKIM on Microsoft 365 without PowerShell | Hacker News Reader

You cannot setup DKIM on Microsoft 365 without PowerShell

github.com

34 pointsvarun_chopra26 comments

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.

Also true for allowing email addresses with "+".

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.

> from the issue discussion we can see that it is indeed possible to do this without PowerShell

Read the whole discussion[1]. It used to be possible to do this without PowerShell, but that's no longer the case.

[1] https://github.com/MicrosoftDocs/microsoft-365-docs/issues/1...

That's pretty disappointing, everyone and his dog running any sort of hosting company allows customers to set this kind of stuff from a web UI.

It's probably a nod to the complexity and complications of running and developing office365.

This is a carry over from Exchange / via the EMC. That is why. Exchange Online/EXO was really developed to be a role on an Windows Server.

DKIM == Domain Keys Identified Mail, i.e. a mechanism so that email can prove it comes from the domain that it claims to come from.

(I can't be the only person here who has never heard of this acronym before.)

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

Per the later comments on the issue, the documentation on doing it in Azure Console is no longer accurate. This makes Powershell the only option.

Seems like not a problem? Help me understand the problem? Someone would rather click around? No access to power shell?

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.

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.

Really? I've never heard that before and a quick search has not come up with anything to back that claim.

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.

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.

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

Powershell runs on MacOS and Linux, too

MacOS: https://docs.microsoft.com/en-us/powershell/scripting/instal...

Linux: https://docs.microsoft.com/en-us/powershell/scripting/instal...

I'm not sure what you mean by "not possible without a Windows machine."

You can also get a Powershell web shell through the Azure Portal.

Some modules are only compatible with the Windows version of PowerShell.

But the EXO module is not one of those Windows-only modules.

Of course. It's amazing the FUD the anti-Windows people will spread!

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.

My national-scale organization has Windows, but my unit doesn't. What might seem very, very unlikely to you is reality to other people.

Reply on news.ycombinator.com