Office 365 Need to Share Calendar Again
question
Calendar sharing issue
I accept a user who has already shared her Outlook calendar with three people, nonetheless when she tries to share with a new person within the organisation she gets the post-obit
Yous don't have permission to share your agenda with user@domain.com
She has tried in Outlook and outlook.office.com and both give the same mistake.
Our default sharing policy has not been changed and other users are able to share their own calendars. What could cause this?
office-outlook-itpro part-exchange-online-itpro
We do not have any segmentation or information barriers in place. I have now been made aware the user she is trying to share her calendar with had access but it stopped working, the consul lost visibility of the calendar so the share permissions were removed. Once this was washed she was no longer able to share her agenda with anyone.
Simply this one user is affected, others are able to share without bug
How almost assigning permissions via powershell, does information technology piece of work?
Add together-MailboxFolderPermission -Identity ayla@contoso.com:\Agenda -User julia@contoso.com -AccessRights Editor -SharingPermissionFlags Consul
0 Votes 0 ·
Powershell fails besides, same error message saying I don't take permission to share the mailbox. I am using a Global administrator business relationship in an EXOPsession
1 Vote i ·
I'm having a similar result. Certain users calendars cannot be granted permissions to other users through Powershell add-mailboxfolderperssion. The users themselves can add permissions in Outlook.
I was able to resolve the result by checking all the users showing to have access to my users calendar. Come to discover out i user that was showing no longer existed in O365. I removed the users access using powershell control 'Remove-MailboxFolderPermission' yesterday and upon checking this morning my user now tin can add users to her calendar permissions in Outlook. I checked OWA since I all the same have access and I am no longer getting an error there besides.
A Solution that has worked for me.
I added the shared agenda to Public Folders, instructed my staff appropriately. One time they have accessed the calendar one time via the public folders they can then right click on the calendar select add to favourites so they are able to admission the calendar via the normal calendar icon. I found that if they didn't access the calendar in public folders first, they could still admission the calendar but the entries lacked detail and only showed as busy.
question details
Related Questions
Source: https://docs.microsoft.com/answers/questions/221159/calendar-sharing-issue.html
I accept this exact same issue, although my user tin can't share her calendar with anyone at all not only new people. Maybe a broader Office 365 outcome?
i Vote i ·
So later on trying what has been suggested, and a few other things I idea may help, this event is nevertheless there. Using powershell results in the exact same failure, same bulletin and result.
I created a new account to test if this was a wider issue, no problems with the new account. I can share this new calendar with anyone within the organization including the user who is unable to share her own agenda.
I also tried changing the permissions for people the problem calendar is shared with, this also fails with the message "The sharing invitation couldn't be updated. Please endeavor over again."
Equally previously stated, when trying to add share admission to the calendar it fails with the message "Y'all don't have permission to share your agenda with user@email.com"
One affair I noticed is the user is listed as a reviewer of her own calendar but I don't run into any way to modify this to make her possessor of the calendar.
Does anyone have any new ideas?
1 Vote i ·
Microsoft just released a new switch for the Remove-MailboxFolderPermission cmdlet, which might aid here. Endeavor running this:
0 Votes 0 ·
Thanks, I would try that but the migration I started yesterday is still non finished. Information technology keeps saying it has stalled due to source deejay latency. Thanks for using deadening disks Microsoft.
I uncertainty in that location is any way to cancel the migration so I'm now at the mercy of Microsoft and take to wait until it either times out or completes.
0 Votes 0 ·
Prove more comments
That did non work either.:
0 Votes 0 ·
Sharing policies do not bear upon intra-organizational sharing. Are you perhaps using GAL partitioning/information barriers within your system?
I suppose yous tin effort adding permissions direct via PowerShell, and include the -SharingPermissionFlags/-SendNotificationToUser to emulate the Outlook sharing experience.
0 Votes 0 ·
I opened a instance with MS about this probably four weeks ago, other than determining it is merely the Default calendar' that is having the issue in that location has non been much in the way of a fix. It has been escalated ALOT and then nosotros will see.
I will update if it ever gets fixed.
0 Votes 0 ·
Hi, is that stock-still at present?
We have tried several solutions just the biggest progress is that @GarethDavies-6974 can share the calendar on Outlook by clearing all folder permissions of the mailbox via powershell.
I just wonder if all of your problems occur with i specific mailbox?
You might need to contact O365 back end team to repair the mailbox, or creating the mailbox and importing his pst file to a new mailbox. Kind of a quick workround.
0 Votes 0 ·
No, the issue is NOT resolved.
It is a unmarried mailbox, at to the lowest degree I simply know of ane with the issue.
Microsoft support told me to migrate the mailbox to a new database, despite saying this is no longer available. I had already done this and it took days. They offered null else.
I can't delete and recreate the mailbox for a number of reasons, only beside everything else the size of the box is over 15GB, I can't consign this to a pst and I am not going to spend days exporting 2GB chunks, plus the calendar has a high volume of recurring meetings, these never import correctly and so it would create more problems than information technology would resolve.
0 Votes 0 ·