Was this page helpful?
Additional feedback?
1500 characters remaining
Export (0) Print
Expand All



Topic Last Modified: 2015-10-15

This is an old version of the topic. To see the current version, change the (v=exchg.150) value in the URL to (v=exchg.160).

This cmdlet is available only in Exchange Online Protection.

Use the Set-EOPGroup cmdlet to modify general group object attributes in Microsoft Exchange Online Protection (EOP) standalone. This cmdlet isn't available in Exchange Enterprise CAL with Services (EOP Premium). In EOP Premium, use the Set-Group cmdlet.

Typically, EOP standalone customers that also have on-premises Active Directory organizations would use directory synchronization to create users and groups in EOP. However, if you can’t use directory synchronization, then you can use cmdlets to create and manage users and groups in EOP.
This cmdlet uses a batch processing method that results in a propagation delay of a few minutes before the results of the cmdlet are visible.

For information about the parameter sets in the Syntax section below, see Syntax.

Set-EOPGroup [-ExternalDirectoryObjectId <String>] [-Identity <GroupIdParameter>] [-ManagedBy <String[]>] [-Notes <String>] [-Organization <OrganizationIdParameter>]

This example sets the Notes property to indicate the last time that the group was updated.

Set-Group -Identity "Legal Department" -Notes "Group members updated June 1, 2014"

You need to be assigned permissions before you can run this cmdlet. Although all parameters for this cmdlet are listed in this topic, you may not have access to some parameters if they're not included in the permissions assigned to you. To see what permissions you need, see the "Distribution Groups and Security Groups" entry in the Feature permissions in EOP topic.


Parameter Required Type Description




The Identity parameter specifies the distribution group or mail-enabled security group that you want to modify.

You can use any value that uniquely identifies the group object. For example:

  • Canonical DN

    Example: Atlanta.Corp.Contoso.Com/Users/Marketing

  • Display name

    Example: "Marketing Department"

  • Distinguished name (DN)

    Example: CN=Marketing,CN=Users,DC=Atlanta,DC=Corp,DC=contoso,DC=com

  • Domain\<account name>

    Example: Atlanta\Marketing

  • GUID

    Example: fb456636-fe7d-4d58-9d15-5af57d0354c2

  • Name

    Example: "Marketing Department"

  • Security Account Manager (SAM) account name

    Example: Marketing

  • Security identifier (SID)

    Example: S-1-5-21-2566577876-3854474493-3520236071-1531




This parameter is reserved for internal Microsoft use.




The ManagedBy parameter specifies one or more group owners. A group must have at least one owner.

This parameter accepts the following values:

  • Alias

    Example: JPhillips

  • Canonical DN

    Example: Atlanta.Corp.Contoso.Com/Users/JPhillips

  • Display Name

    Example: Jeff Phillips

  • Distinguished Name (DN)

    Example: CN=JPhillips,CN=Users,DC=Atlanta,DC=Corp,DC=contoso,DC=com

  • Domain\Account

    Example: Atlanta\JPhillips

  • GUID

    Example: fb456636-fe7d-4d58-9d15-5af57d0354c2

  • Immutable ID

    Example: fb456636-fe7d-4d58-9d15-5af57d0354c2@contoso.com

  • Legacy Exchange DN

    Example: /o=Contoso/ou=AdministrativeGroup/cn=Recipients/cn=JPhillips

  • SMTP Address

    Example: Jeff.Phillips@contoso.com

  • User Principal Name

    Example: JPhillips@contoso.com

You can specify multiple owners by using the following syntax: @("<user1>","<user2>"...). The values that you specify will overwrite the current list of owners.

The users specified with the ManagedBy parameter aren't automatically members of the group. If you want any of the owners to be added as members of the group, you need to add them by using the Update-EOPDistributionGroupMember cmdlet.




The Notes parameter specifies additional information about the group.




The Organization parameter is reserved for internal Microsoft use.

To see the input types that this cmdlet accepts, see Cmdlet Input and Output Types. If the Input Type field for a cmdlet is blank, the cmdlet doesn’t accept input data.

To see the return types, which are also known as output types, that this cmdlet accepts, see Cmdlet Input and Output Types. If the Output Type field is blank, the cmdlet doesn’t return data.

Was this page helpful?
(1500 characters remaining)
Thank you for your feedback
© 2015 Microsoft