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(41.6, 6%, 14%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EJM%3C/text%3E%3C/svg%3E)
It appears that the ability to call the 'set-mailboxregionalconfiguration' cmdlet when using certificate based authentication with exchangeOnline v2 module stopped working sometime in the last couple of weeks (early/mid-April). Prior to that it was working just fine in our provisioning scripts. If I authenticate manually with a global admin account to exchangeOnline, the cmdlet works fine. Just wondering if anyone else has run into this and if there's a work-around? Have tried adding more rights on the app registration side of things to no avail. I know there's some other cmdlets that are also broken (rights-wise) via certificate based auth.
Thanks.
Hello JohnMeyers,
This may be related with recent releases of the EXO v2 Module
To report bugs please check: https://learn.microsoft.com/en-us/powershell/exchange/exchange-online-powershell-v2?view=exchange-ps#report-bugs-and-issues-for-the-exo-v2-module
But first I would recommend to update the module as per instructions in the official article:
------------------------------------------------------------------------------------------------------------------------------
--If the reply is helpful, please Upvote and Accept as answer--
Thanks for the comment LT2700.
I've already updated to the latest supported release of EXO v2 under Powershell 5.1. This was working just fine until April 25th when I started getting the 'unauthorized' error when issuing the command. An example looks like,
==
Error on proxy command 'Set-MailboxRegionalConfiguration -Identity:'some.user@our.domain' -Confirm:$False
-Language:'en-US' -TimeZone:'Eastern Standard Time'' to server SN6PR01MB3950.prod.exchangelabs.com: Server version
15.20.5186.0000, Proxy method PSWS:
Request return error with following error message:
The remote server returned an error: (401) Unauthorized..
[Server=MW2PR0102MB3498,RequestId=5f589adf-a041-4674-8b51-d97a55b80b40,TimeStamp=5/2/2022 6:51:12 AM] .
I've actually updated the api permissions to give it full readwrite on just about everything I can think of on the ExchangeOnline side of things. Again, this was working just fine and then stopped on April 25th with no changes to our environment during that timeframe.
I ran into to something similar with some group related cmdlets that was a known issue with no fix available.
Ok, so some additional testing this morning and I come to find out it's actually working this morning without error. Was trying out a newer preview release on a fresh install and it was working, so rolled back to the non-preview release and it's also working. Just tried it on my production host and it's working there also, so Microsoft must have fixed something related to this. At least it only took them a little over a week to get it sorted out. Will post a follow-up if it starts failing again.
So I reenabled this operation using 'set-mailboxregionalconfiguration' in my production side and just this past week started having some additional issues with it. Basically the time to execute this command is all over the place from taking 30 seconds, 5-10 minutes to complete, to just hanging in one case. Really unstable operation of this cmdlet, so I've since disabled it again in my code. Starting to lose faith in Microsoft's ability to execute the changes they're implementing recently.
![](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(256, 74%, 34%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ERM%3C/text%3E%3C/svg%3E)
You should probably add the office-exchange-server-administration tag to your original post. The problem you have is with a product-specific cmdlet (written by the product group). While the cmdlet may be run in PowerShell it's not part of the delivered PowerShell product.
The Exchange SMEs will have a much better understanding of the environment in which that cmdlet operates.
Thanks for the suggestion, definitely appreciate that. Somewhat new to this site and still having issues with a fair number of the screens and update options.