Applies to: Exchange Server 2010 SP2
Topic Last Modified: 2012-07-23
This topic explains how to manage tenant organizations by using either the organization scope or the organization context.
Organization Scope
The organization scope allows you to specify the organization in which you can perform an action. The scope is definable at the Identity parameter level. For example, if you want to view information about Tony Smith's mailbox for a tenant organization named Humongous Insurance, use the following syntax:
Copy Code | |
---|---|
Get-Mailbox -Identity "HumongousInsurance\tonysmith" |
You can also use wildcard characters to specify the scope. For example:
Copy Code | |
---|---|
Get-AddressList -Identity "Hum*\*" |
The following parameter types allow you to define the organization scope:
Note: |
---|
In the cmdlet reference help files, the parameter type is listed in the third column. |
- AcceptedDomainIdParameter
- AddressBookBaseIdParameter
- AddressListIdParameter
- ADRawEntryIdParameter
- ADSchemaObjectIdParameter
- AdSiteIdParameter
- AdSiteLinkIdParameter
- AvailabilityAddressSpaceIdParameter
- ClientAccessServerIdParameter
- ContactIdParameter
- ContainerIdParameter
- ContentFilterPhraseIdParameter
- DatabaseIdParameter
- DetailsTemplateIdParameter
- DistributionGroupIdParameter
- DistributionGroupMemberIdParameter
- DsnMessageIdParameter
- DynamicGroupIdParameter
- ECIdParameter
- ELCContentSettingsIdParameter
- ELCFolderIdParameter
- EmailAddressPolicyIdParameter
- ExtendedRightIdParameter
- ForeignConnectorIdParameter
- GeneralMailboxIdParameter
- GeneralRecipientIdParameter
- GlobalAddressListIdParameter
- GroupIdParameter
- IPAllowListProviderIdParameter
- IPBlockListProviderIdParameter
- IPListEntryIdentity
- LogonableObjectIdParameter
- MailboxIdParameter
- MailboxOrMailUserIdParameter
- MailboxPolicyIdParameter
- MailboxServerIdParameter
- MailContactIdParameter
- MailUserIdParameter
- MapiIdParameter
- MessageClassificationIdParameter
- OfflineAddressBookIdParameter
- OrganizationalUnitIdParameter
- OutlookProviderIdParameter
- ReceiveConnectorIdParameter
- RecipientIdParameter
- RecipientTypeFilter
- RemoteDomainIdParameter
- RoleServerIdParameter
- RoutingGroupConnectorIdParameter
- SecurityPrincipalIdParameter
- SendConnectorIdParameter
- ServerBasedIdParameter
- ServerIdParameter
- ServerRoleFilter
- StorageGroupIdParameter
- StoreMailboxIdParameter
- SystemAttendantIdParameter
- TransportServerIdParameter
- UserContactIdParameter
- UserIdParameter
- VirtualDirectoryIdParameter
- X400AuthoritativeDomainIdParameter
Organization Context
The organization context allows you to identify the organization in cmdlets that don’t include the Identity parameter. The context is defined by using the Organization parameter.
The Organization parameter specifies the organization on which you perform actions. This parameter doesn’t accept wildcard characters, and you must use the exact name of the organization.
To find all the cmdlets that take the Organization parameter and that you have permission to use, run the following command:
Copy Code | |
---|---|
Get-ManagementRoleEntry *\* -Parameters Organization |
For detailed syntax and parameter information, see Get-ManagementRoleEntry.
Examples
The following examples show you how to use the organization scope and the context for tenant organizations.
Example 1
This example returns all accepted domains for the organization Humongous Insurance, including all the accepted child domains within the organization:
Copy Code | |
---|---|
Get-AcceptedDomain -Identity HumongousInsurance\* |
This example returns all accepted domains for Humongous Insurance.
Copy Code | |
---|---|
Get-AcceptedDomain -Organization "HumongousInsurance" |
Example 2
This example creates the address list Contoso_AL for the Contoso organization.
Copy Code | |
---|---|
New-AddressList -Name "Contoso_AL" -IncludedRecipients AllRecipients -Organization Contoso |
For detailed syntax and parameter information, see Get-AcceptedDomain and New-AddressList.