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(25.6, 87%, 12%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EJ%3C/text%3E%3C/svg%3E)
Hey folks,
Exchange online / OWA environment (fully online no hybrid) - have 20 or so users all accessing various shared mailboxes with various shared subfolders all with different permissions. All using OWA. This has been working absolutely fine for the past year until Monday morning when all of a sudden 4 users in various countries couldn't access the usual folders with permissions. Only way they can have access is by delegating full mailbox access which I can't do as there are restricted folders in those mailboxes which they don't have user permissions to view/access.
Here's odd - make a brand new user with permissions - and they can't access either.
Make a new mailbox/share and those users can't access.
All permissions look correct through OWA mailbox permissions
All permissions look correct when adding the shared mailbox to Outlook desktop and querying permissions.
All permissions look correct when querying using Get-mailboxpermission and Get-MailboxFolderPermission through Powershell
Microsoft techs been on this since Monday and today we're trying New-MoveRequest but so far after 4 hours that doesn't seem to have fixed anything.
Even making a new licenced user and new shared mailbox/shared sub folders - still broken.
These users can 'see' the subfolders (as long as their permissions include 'folder visible') but cannot access.
users can even create subfolders within those very folders that they can't access, and then subsequently have no access to the new created ones, even though they are marked as 'owner'
Any clues or even wild experiments to try, gratefully received !
Much thanks
![](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(284.8, 17%, 37%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EYS%3C/text%3E%3C/svg%3E)
Hi @JerryMeister ，
have 20 or so users all accessing various shared mailboxes with various shared subfolders all with different permissions. All using OWA. This has been working absolutely fine for the past year until Monday morning when all of a sudden 4 users in various countries couldn't access the usual folders with permissions.
By this, do you mean except the "4 users", the other users out of the "20 or so" can still access the shared mailboxes as usual? If this is the case, how about testing on one machine with both a problematic user's account and a normal user's account to see the result? This helps eliminate whether the issue is related to a particular machine.
Besides, is there any detailed error message when the issue occurs to the 4 users?
Can they access the shared folders properly in the Outlook desktop client?
If an Answer is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.
Hey thanks for joining the conversation mate.
At the moment it's looking like ALL users (well, at least those that have bothered to test for me !) cannot access any shared mailboxes UNLESS they are given full delegate access.
No-one has/uses Outlook desktop app so I can't check that sorry, though when I load a shared mailbox account into my own desktop app all the permissions appear as they should for the users.
The only error is the 'Access Denied' padlock and key image when they try and access the folder.
![](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(182.40000000000003, 6%, 27%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EM%3C/text%3E%3C/svg%3E)
Hello,
I have the same issue since today (Monday, everything was fine on Friday).
I have been using 5 different shared mail boxes the last few years and today I have only access to one (+ my main mail box)
The access hasn’t been changed. (We checked that and it is fine).
Only on my mobile phone I am still able to see all boxes but on any computer devise the system say that a do not have the access to this.
Thanks for your help.
Marie
![](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(259.20000000000005, 66%, 35%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ENS%3C/text%3E%3C/svg%3E)
Hi @MBGic
Did your issue ever resolve? I missed tagging you in my post below.
I can no longer access user mailboxes converted to shared after 6 years of everything working fine.
Microsoft is giving me the run-around for 10 days now.
Thanks,
-Nick
![](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(310.4, 67%, 40%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ESD%3C/text%3E%3C/svg%3E)
Same issue here. I have several users, making use of OWA who can suddenly not access shared mailboxes. (they can in the Outlook client, just not in OWA)
Been following this thread since Monday. Happy to see I'm not alone. Was hoping for resolution by now.
Editing permissions, doesn't seem to change anything.
Please, a fix is wanted.
I feel for you man ! Good you can still access through Outlook Client. If you have the option - I had my agent/re-seller escalate the issue to premium support, that was the only way to get stuff moving along. It still took from Monday morning till Wednesday lunch to get fixed but compared to the week wasted beforehand going back and forth doing the all the same tests and powershell commands I'd already run, it was a good call.
In the end I had 3 cases open and escalated PLUS the premium support case - just keep banging on at them mate, it's just shoddy how the system leaves you hanging. Open another case requesting escalation. I feel for the customer support peeps that we speak to who really can't do much more beyond the basic and get fed whatever from higher up the chain to the lofty heights of engineers that can't give a straight answer or acknowledge a stuff up or a fault.
I'm assuming you've checked sub folder and mailbox permissions through powershell too ?
And all your users have minimum Reviewer level permissions at INBOX level of shared mailboxes ? (just ticking the boxes here, excuse if you've done that a million times for tech support already :) )
Fingers crossed for you mate.
J
Hi @Sven Dijkstra ,
As has been mentioned above by @JerryMeister , you have already checked the permissions as we discussed earler, right?
If this is the case, considering that Jerry's issue was just "resolved for no apparent reason", I personally assuming maybe any change was made from the backend of Exchange online that finally brought everything back to normal. So for your situation, I'd recommend giving it some time and see if there would be any improvement. If the problem persists, you may try to open up a new thread or start a service request for this issue.
If an Answer is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.
Hey folks, finally resolved for no apparent reason !
During testing yesterday morning I noticed shared mailboxes were suddenly available. A quick survey from users as they came online around the different timezones reported all was good. Good news all round.
What I feel a lot of umbrage about is not only the glacial slowness that MS took to fix this (9 days to resolve from first notification) but now the distinct lack of any follow up and reporting as to what actually happened, why it took so long to fix and what's going to be done to stop it happening again. I swear we just put up with being treated like donkeys even though we pay for the service, coz we've nowhere else to go to and the dead silent brick wall is too hard to keep banging our heads against. Previously I had the whole company with Fastmail before this and for the past year I have had MANY opportunities to regret my decision to bring our email and associated messagaging etc over to exchange and OWA. The cons are slowly beginning to outweigh the convencience of the pros.
Anyhoo, if I do happen to glean any further useful info I will pass it on here for the benefit of others. In the meantime thanks heaps for your help and thoughts along the way.
Hi @JerryMeister ,
During testing yesterday morning I noticed shared mailboxes were suddenly available. A quick survey from users as they came online around the different timezones reported all was good. Good news all round.
Great to know that the issue was finally resolved and thanks for keeping us posted here!
OK this is as much as I could get back from the Frontline Support Team that were dealing with my case:
As explained, our senior team members had analyze the Fiddler logs and they were able to identify the error for access denied: {"Header":{"ServerVersionInfo":{"MajorVersion":15,"MinorVersion":20,"MajorBuildNumber":4394,"MinorBuildNumber":22,"Version":"V2018_01_08"}},"Body":{"Conversations":null,"FolderId":{"__type":"FolderId:#Exchange","Id":"REMOVED"},"MessageText":"Access is denied. Check credentials and try again., Cannot query rows in a table.","ResponseCode":"ErrorAccessDenied","ResponseClass":"Error"}}
I need to raise another ticket to get a Root Cause Analysis (which displays a remarkable lack of responsibility from MS but there you go) but for now - @Sven Dijkstra , maybe get them to request Fiddler Logs and Step Recorder while you try and gain access to the blocked mailboxes using OWA. Looking at the log extract they gave me there's obviously an issue with user credentials getting passed to mailboxes, and - I'm guessing here - from the Cannot query rows in a table line, I'd say some corrupted user credentials database, but I'm spitballing on that one!
Let us know how you go man !
Hey @Sven Dijkstra
I tried to get some more info that would maybe help you in your case, but this is what I got back in response!
I have further checked with my senior team regarding this and as it was resolved suddenly, I’m afraid we are not able to identify what exactly was done from the backend which resolved the issue. For other tenants that are having similar issue, you could advise them to contact MS support so that we could collect further information from them and engage our backend team in the troubleshooting process.
How the heck MS manages to run such a huge network based on some magic is beyond me :)
Anyhoo, hope you get yours sorted man, look forward to hearing more.
Cheersy
J
Just FYI - spoke with one of the case managers and if anyone else has this problem - you can quote my case numbers to find the solution and speed your issue along:
original report Case #:26835973
request for escalation Case #:26915057
Frontline Support team case Case #:26936858
All the best !
J
Hi @JerryMeister ,
Really appreciate it for these information! It would definitily be helpful to others who encounter a similar issue.
By the way, I just tried combining your sharing into this answer, and if you don't mind, you can click "accept answer" under your post to make it easier for others reading this thread to quickly find the useful information : )
Hi @Sven Dijkstra ,
Just wondering how things are going on with your issue. In case it hasn't been fixed, agree with Jerry that you can open up a support ticket referencing to the case numbers he shared above, so that the backend team can be involved to help troubleshoot. Hope you issue can get resolved soon!
If an Answer is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.
Done, thanks for that
J
Hi @JerryMeister @Yuki Sun-MSFT @Sven Dijkstra
I'm having a similar issue in my tenant suddenly since 10 days ago. This post was one of the first things I found while trying to research.
We moved from Exchange on-prem to hybrid 6 years ago. Since then we regularly convert user mailboxes into shared mailboxes and delicense them. We are up to 1,447 mailboxes like this. We regularly have users accessing the shared mailboxes with the associated username and password via outlook.office.com, for many different reasons.
Suddenly July 19 2022, all these users started getting an error "OwaUserHasNoMailboxAndNoLicenseAssignedException" and cannot access the mailboxes with username and password.
Microsoft support is giving me the exact same run around "this is by design" "you can't use credentials to access shared mailbox" "you must apply full access permissions" but cannot account for this workflow working just fine over the past 6 years. They say they aren't allowed to open your old cases to research.
The current T2 rep is telling me it started happening in his tenant about 1.5 years ago and they just accepted that Microsoft made a change and it is replicating. I refuse to accept this without documentation from Microsoft saying they've changed it.
Desperate, I'm back to try and get any insight you may have after all this time, is it still working for you?
-Nick
Continuing back and forth with MS and they have come this to me and said 'this is by design' - 'this' being shared folder permissions in a mailbox sub folders that has worked absolutely fine for a year or so. Which sounds like a fob-off to me.
Can I ask if anyone else is sharing shared-mailbox sub-folders with per-user permissions set in OWA or PS and those users NOT being full-access delegates ?
The MS engineer said to give users delegate access instead as 'that's how the system is designed to work' but in trying that out anyone with delegate access gets full mailbox permission and the OWA folder permissions then get ignored.
I feel like MS is giving me the run around here - this was working fine until last Monday morning and since then no-one in our tenant can access shared mailbox folders except the admins with full delegate access.
Cheers all
J
Hi @JerryMeister ，
May I know if you have checked and made sure the users also have proper permissions to the parent folders and root folder of the shared subfolders?
I just tried it in my test tenant and here's what I experienced:
Feel free to let me know if I have misunderstood anything in my test procedure.
If an Answer is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.
Hey thanks so much for that - yes pretty much as that except I can't do a log-on for the shared mailbox (as it's a shared mailbox, not a licenced user)
So here's how the permissions are set/checked:
click my profile pic / choose "open another mailbox"
put in the username of the shared mailbox / mailbox opens in a new tab
right click Inbox and set 'permissions publishing editor' (currently this throws up an error saying "can't complete your request / Permissions can't be saved for folder Inbox" (but that used to be how it worked)
I then did that for all users/sub folders in the shared mailbox.
If I right-click the Root 'Folders' above inbox it gives me the permission box again but strangely enough shows MY email address and not the shared mailbox. Engineers confirmed this happens to them too.
It's like, all of a sudden the whole shared mailbox system/structure is just broken for us.
Engineers have just come back with some PS commands to try so I will give that a go and report back.
Thank you for your valuable time and input, it's very much appreciated
J
Hi @JerryMeister ，
Engineers have just come back with some PS commands to try so I will give that a go and report back.
Hopefully the commands can work for you.
And in case the issue persists, would you mind sharing the current permission settings from your side via either the OWA screenshots or output of Get-Mailboxfolderpermission and I can help test on my end to see how things are going. Do remember to remove all personal information involved when sharing the details to protect your privacy data.
If an Answer is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.
Thanks YukiSun! Just run Using Get-EXOMailboxFolderPermission on a couple of sample mailboxes and all permissions show as they should - here's quick sample:
Get-EXOMailboxFolderPermission -Identity sharedmailbox@keyman .com:\ -User user1@keyman .com
Identity : sharedmailbox:\
FolderName : Top of Information Store
User : user1@keyman .com
AccessRights : {PublishingEditor}
SharingPermissionFlags :
Get-EXOMailboxFolderPermission -Identity sharedmailbox@keyman .com:\INBOX -User user1@keyman .com
Identity : sharedmailbox:\INBOX
FolderName : Inbox
User : user1@keyman .com
AccessRights : {Editor}
SharingPermissionFlags :
Thanks for looking at it mate, much appreciated.
J
some more tests this morning - something is definitely broken !
First off I assigned a Microsoft 365 Business Basic licence to a previous shared mailbox (tempmailbox@keyman .com)
Then made permissions for user test@keyman .com to access (that also has MS365BB licence)
No access !
THEN, I shared my own Inbox and top level folder to temp user - No access ! what's more, even though the user can see the presence of my inbox, they only see a single sub folder, not all of them - and permissions are same.
Also tested assigning reviewer permissions to default and anonymous user across mailbox folders. Again, no access.
Hi @JerryMeister ,
Just run Using Get-EXOMailboxFolderPermission on a couple of sample mailboxes and all permissions show as they should - here's quick sample:
From the output, the folder permissions look good to me as well. I've also tested using a shared mailbox in my tenant with the same permission as yours and it works on my end:
With the permissions above, User1 has no issue accessing the Inbox folder of the shared mailbox:
Considering that it's a recently occurred issue in your environment, was there any changes made in your Exchange organization right before the issue started?
If an Answer is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.
Hey YukiSun thanks for staying on it - yup that's the strange thing; everything was left fine on Friday evening 30th July - Monday 2nd August people couldn't access shared folders that had been working fine for the past year. Nothing was changed by us over the weekend (I'm the only admin). It all seems very broken. Had our re-seller run pretty much all the same tests yesterday AND changing permissions via Outlook desktop client; still broken.
@Nick Sheen Hey man sorry to hear you're having the same issue. I escalated it with both MS AND got my reseller involved too. It is definitely a bug and not a 'working as intended' - but the fact they 'magically fixed it' then could not report how it was actually fixed leads me not to be of any help to you sorry Nick. But get it escalated and make a lot of noise and eventually the right people will take note and sort it out. Frustrating as all hell mate. And ridiculous that you have to jump up and down just to get some basic-level fixes. Good luck man ! Please come back here and share what happens. I was well in the dark when it happened to my tenant so hopefully at least you know you have company :)