Share via

Office365 Group set calendar to be read-only for members

Anonymous
2018-05-30T22:29:58+00:00

I've created an Office 365 group and wish to set the calendar to be read-only for the members.

There is a powershell command Set-UnifiedGroup -Identity "Group Name" -CalendarMemberReadOnly That is supposed to set this property per the cmdlet documentation, but when I run it I get the following:

Set-unifiedgroup -Identity "Group Name" -CalendarMemberReadOnly

WARNING: The command completed successfully but no settings of

'groupname_some_long_string' have been modified.

And if I do Get-UnifiedGroup | format-list that property is not set:

RunspaceId                             : run spaceid number

AccessType                             : Private

AutoSubscribeNewMembers                : True

AlwaysSubscribeMembersToCalendarEvents : True

CalendarMemberReadOnly                 :

This is the documentation:

The CalendarMemberReadOnly switch specifies whether to set read-only Calendar permissions to the Office 365 Group for members of the group.

  • To set read-only Calendar permissions, use the CalendarMemberReadOnly switch without a value.
  • To remove read-only Calendar permissions, use this exact syntax: -CalendarMemberReadOnly:$false.

Why isn't this working?

Outlook | Windows | Classic Outlook for Windows | For home

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments

Answer accepted by question author

Anonymous
2018-06-02T16:13:14+00:00

Well, I made a test group, and it works as expected:

  1. the calendar is visible in OWA
  2. accessible by looking for the group
  3. only writable by the owner for the group

members are able to enter events in both OWA and Outlok 2016, but these events are only visible to them.

Still,  when I run "Get-UnifiedGroup |fl *Calendar*" the CalendarMemberReadOnly and CalendarURL properties are still null.

We do have a hybrid Exchange environment, but nothing I've found on that indicates that this could cause the discrepancy I'm seeing.

It works though, and is behaving as desired: only the owners can post events to the group, so I'll declare this 'solved-ish'

If things don't work correctly when I expand the to the wider group of users, I'll raise the issue with our official O365 support.

Was this answer helpful?

1 person found this answer helpful.
0 comments

5 additional answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2018-05-31T07:30:00+00:00

    Hi Bruce,

    Please use an account to create a calendar event in OWA and check if it works. Please note that it may take some time. And I would give you a screenshot of mine. For your reference:

    And you can refer the link below: 

    https://docs.microsoft.com/en-us/powershell/module/exchange/users-and-groups/set-unifiedgroup?view=exchange-ps

    If the issue persists, please check whether you connected to Exchange Online Powershell correctly. Besides, please let me know what group it is. (Office 365 group, Security group or Distribution group)

    Regards,

    Carlos

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  2. Anonymous
    2018-05-30T23:38:57+00:00

    Hi Bruce,

    Thanks for your details, I have tested on my side and it works properly. Here is something I need to clarify:

    1. The cmdlet won't allow group members to edit calendar. But if users have group owner permission, they can still edit the calendar.
    2. The cmdlet only works for users in OWA(Outlook Web App). Based on my test, users can edit the calendar in Outlook desktop client, but it won't sync.

    Regarding to this feature, our related engineers admit that it is in the plans. In this situation, it is suggested to vote and leave your thoughts via the link. Thanks for your understanding. 

    Regards,

    Carlos

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  3. Anonymous
    2018-06-02T07:38:12+00:00

    Hi Bruce,

    If there is any update, please share when you are free.

    Regards,

    Carlos

    Was this answer helpful?

    0 comments
  4. Anonymous
    2018-05-30T23:52:55+00:00

    Hi Bruce,

    Thanks for your details, I have tested on my side and it works properly. Here is something I need to clarify:

    1. The cmdlet won't allow group members to edit calendar. But if users have group owner permission, they can still edit the calendar.
    2. The cmdlet only works for users in OWA(Outlook Web App). Based on my test, users can edit the calendar in Outlook desktop client, but it won't sync.

    Regarding to this feature, our related engineers admit that it is in the plans. In this situation, it is suggested to vote and leave your thoughts via the link. Thanks for your understanding. 

    Regards,

    Carlos

    1. This is my desired outcome so this is good
    2. The vast majority of the users in this instance use OWA.

    However when I run the command, NOTHING HAPPENS. I get the error :

    PS C:\Users\johnson> Set-unifiedgroup -Identity **Removed** -CalendarMemberreadOnly

    Creating a new Remote PowerShell session using MFA for implicit remoting of "Set-UnifiedGroup" command ...

    WARNING: The command completed successfully but no settings of

    '**Removed**' have been modified.

    THAT is my issue. Shouldn't Get-UnifiedGroup show that that property is set to True?

    PS C:\Users\johnson> Get-unifiedgroup -Identity **Removed** |fl

    RunspaceId                             : **Removed**

    AccessType                             : Private

    AutoSubscribeNewMembers                : True

    AlwaysSubscribeMembersToCalendarEvents : True

    CalendarMemberReadOnly                 :      <<<<--Apparently NOT set

    CalendarUrl                            :

    Database                               : **Removed**

    ExchangeGuid                           : **Removed**

    ------Personal information removed by moderator to protect your privacy------

    Was this answer helpful?

    0 comments