This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(134.4, 45%, 23%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ENK%3C/text%3E%3C/svg%3E)
Hello,
I have some troubles with getting Set-Mailbox cmdlet to work via new certificate workflow (application + app permissions + roles + certificate + new exchange online preview module).
https://www.powershellgallery.com/packages/ExchangeOnlineManagement/2.0.3-Preview
Is it even possible in this version? If so, what the requirements are?
Thanks in advance!
and you can see that switch if you logon interactively with PS as an Exchange Admin ?
@AndyDavidMVP Well, thanks to you I was able to get the difference between my tenants. The difference lies in Role Groups. My "old tenant" Organization Management role group had fewer management roles assigned than its twin in the other tenant. Corrected that, and voila!
Sounds like something maybe just got messed up on that app? Can you delete and recreate it or was that done already ?
@AndyDavidMVP already performed that. Repeated all the steps with a new app, still the same result (no set-mailbox with AuditEnabled). I even got the token via client_credentials flow using my certificate, put it into PsCredential and created a New-PsSession with it. I thought may be there were some cmdlets that had not been not imported. I entered the session and no, there was no Set-mailbox with AuditEnabled parameter in this session. I am out of thoughts actually.
The only only API Permissions you should see are:
The "Roles and Adminstrators" menu you have in that last image arent the roles assigned to the app, its the roles that can manage it, so the Exchange Admin wouldnt be listed there by default.
@AndyDavidMVP Wow! I repeated the needed steps on my clean tenant and somehow it really worked out. Then, I repeated the steps again for the previous one and, unfortunately, there was no success. Perhaps you have any ideas? Anyway, thank you very much for your help!
@Nikita Krivets , What directory role did you give the app in Azure? The Exchange role should allow that. I just double-checked and I have access to that parameter connecting through the Azure app.
@AndyDavidMVP The assigned role is Exchange Administrator. If you go to the Roles and administrators menu and select Exchange Administrator role, you can see your app in the list. However, if you go to the Roles and administrators menu through you app registration page, the role won't be listed there as an assigned one.
Here is the list of assigned Exchange permissions.
The role:
What I am talking about when I have said the role is not shown as assigned:
I haven't seen that. I assume the app has been assigned the Exchange role.
What happens when you use set-mailbox? I just tested and it works fine for me.
@AndyDavidMVP Thanks for your reply. Yeah, Set-Mailbox now works (I believe I had to wait a bit). But Set-Mailbox with AuditEnabled parameter doesn't work. I think that is a permission problem.
PS C:\Users\administrator> Set-Mailbox azuremailbox -MailTip "asdasd" (Just an example. Works fine.)
PS C:\Users\administrator> Set-Mailbox azuremailbox -AuditEnabled $true A parameter cannot be found that matches parameter name 'AuditEnabled'.
If I use any user account with Audit Logs exchange management role, Set-mailbox myMailbox -AuditEnabled $true ($false) works fine