You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This example is useful with an untrusted cross-forest Availability service, or if detailed cross-forest free/busy service isn't desired. Enter a username and password when you're prompted by the command. For an untrusted cross-forest configuration, make sure that the user doesn't have a mailbox.
51
+
In on-premises Exchange, this example is useful with an untrusted cross-forest Availability service, or if detailed cross-forest free/busy service isn't desired. Enter a username and password when you're prompted by the command. For an untrusted cross-forest configuration, make sure that the user doesn't have a mailbox.
This example is useful with a trusted cross-forest Availability service. The contoso.com forest trusts the current forest, and the specified account connects to the contoso.com forest. The specified account must be an existing account in the contoso.com forest.
58
+
In on-premises Exchange, this example is useful with a trusted cross-forest Availability service. The contoso.com forest trusts the current forest, and the specified account connects to the contoso.com forest. The specified account must be an existing account in the contoso.com forest.
This example is useful with a trusted cross-forest Availability service. The contoso.com forest trusts the current forest and uses the service account (typically the local system account or the computer account) to connect to the contoso.com forest. Because the service is trusted, there is no issue with authorization when the current forest tries to retrieve free/busy information from contoso.com.
65
+
In on-premises Exchange, this example is useful with a trusted cross-forest Availability service. The contoso.com forest trusts the current forest and uses the service account (typically the local system account or the computer account) to connect to the contoso.com forest. Because the service is trusted, there is no issue with authorization when the current forest tries to retrieve free/busy information from contoso.com.
This example sets up the sharing of free/busy information in Exchange Online. You're requesting to read free/busy information of contoso.com (tenant ID value 9d341953-da1f-41b0-8810-76d6ef905273), and contoso.com is a regular Microsoft 365 organization.
72
+
In Exchange Online, this example sets up the sharing of free/busy information with contoso.onmicrosoft.com (tenant ID value 9d341953-da1f-41b0-8810-76d6ef905273), which is a regular Microsoft 365 organization.
73
73
74
74
## PARAMETERS
75
75
@@ -79,7 +79,7 @@ The AccessMethod parameter specifies how the free/busy data is accessed. Valid v
79
79
- PerUserFB: Per-user free/busy information can be requested. The free/busy data is accessed in the defined per-user free/busy proxy account or group, or in the All Exchange Servers group. This value requires a trust between the two forests, and requires you to use either the UseServiceAccount parameter or Credentials parameter.
80
80
- OrgWideFB: Only default free/busy for each user can be requested. The free/busy data is accessed in the per-user free/busy proxy account or group in the target forest. This value requires you to use either the UseServiceAccount parameter or Credentials parameter.
81
81
- OrgWideFBBasic: Free/busy sharing between tenants that are all in Exchange Online.
82
-
- InternalProxy: The request is proxied to an Exchange in the site that has a later version of Exchange.
82
+
- InternalProxy: The request is proxied to an Exchange server in the site that's running a later version of Exchange.
83
83
- PublicFolder: This value was used to access free/busy data on Exchange Server 2003 servers.
The ForestName parameter specifies the SMTP domain name of the target forest for users whose free/busy data must be retrieved. If your users are distributed among multiple SMTP domains in the target forest, run the Add-AvailabilityAddressSpace command once for each SMTP domain.
99
+
The ForestName parameter specifies the SMTP domain name of the target forest that contains the users you're trying to read free/busy information from. If users are distributed among multiple SMTP domains in the target forest, run the Add-AvailabilityAddressSpace command once for each SMTP domain.
This parameter is available only in on-premises Exchange.
171
171
172
-
The ProxyUrl parameter was used to specify the URL that directed an Exchange 2007 Client Access server to proxy its free/busy requests through an Exchange 2010 or Exchange 2013 Client Access server when requesting federated free/busy data for a user in another organization. When you used this parameter, you needed to set the value of the AccessMethod parameter to InternalProxy.
172
+
The ProxyUrl parameter was used to specify the URL that directed an Exchange 2007 Client Access server to proxy free/busy requests through an Exchange 2010 or Exchange 2013 Client Access server when requesting federated free/busy data for a user in another organization. When you used this parameter, you needed to set the AccessMethod parameter value to InternalProxy.
173
173
174
174
This parameter required that you created the proper trust relationships and sharing relationships between the Exchange organizations. For more information, see [New-FederationTrust](https://learn.microsoft.com/powershell/module/exchange/new-federationtrust).
The TargetAutodiscoverEpr parameter specifies the Autodiscover URL of Exchange Web Services for the external organization, for example, `https://contoso.com/autodiscover/autodiscover.xml`. Exchange uses Autodiscover to automatically detect the correct server endpoint for external requests.
190
+
The TargetAutodiscoverEpr parameter specifies the Autodiscover URL of Exchange Web Services for the external organization that you're trying to read free/busy information from. For example, `https://contoso.com/autodiscover/autodiscover.xml`. Exchange uses Autodiscover to automatically detect the correct server endpoint for external requests.
This parameter is available only in the cloud-based service.
207
207
208
-
The TargetServiceEpr parameter specificies the Exchange Online Calendar Service URL of the external organization whose free/busy informaton you're trying to read. Valid values are:
208
+
The TargetServiceEpr parameter specifies the Exchange Online Calendar Service URL of the external Microsoft 365 organization that you're trying to read free/busy information from. Valid values are:
209
209
210
210
- Microsoft 365 or Microsoft 365 GCC: outlook.office.com
211
211
- Office 365 operated by 21Vianet: partner.outlook.cn
Copy file name to clipboardExpand all lines: exchange/exchange-ps/exchange/Get-AvailabilityConfig.md
+4-7Lines changed: 4 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -14,11 +14,10 @@ ms.reviewer:
14
14
## SYNOPSIS
15
15
This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
16
16
17
-
Use the Get-AvailabilityConfig cmdlet to view information about the sharing of free/busy information in the organization.
17
+
Use the Get-AvailabilityConfig cmdlet to view information about the sharing of free/busy information between organizations:
18
18
19
-
In on-premises Exchange, the cmdlet returns the accounts that are trusted in the cross-forest sharing of free/busy information.
20
-
21
-
In Exchange Online, the cmdlet returns the tenant IDs of organizations that free/busy information is being shared with.
19
+
- In on-premises Exchange, the cmdlet returns the accounts that are trusted in the cross-forest sharing of free/busy information.
20
+
- In Exchange Online, the cmdlet returns the tenant IDs of organizations that free/busy information is being shared with.
22
21
23
22
For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax).
The Get-AvailabilityConfig cmdlet lists the accounts or tenant IDs that have permissions to issue proxy availability service requests on an organizational or per-user basis.
35
-
36
33
You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
37
34
38
35
## EXAMPLES
@@ -49,7 +46,7 @@ In Exchange Online, this examples returns the tenant IDs that free/busy informat
49
46
## PARAMETERS
50
47
51
48
### -Identity
52
-
This parameter is unnecessary. Each organization has only one availability configuration object named Availability Configuration.
49
+
The Identity parameter specifies the availability configuration that you want to view. You don't need to use this parameter, because there's only one availability configuration object named Availability Configuration in any organization.
Copy file name to clipboardExpand all lines: exchange/exchange-ps/exchange/New-AvailabilityConfig.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -14,7 +14,7 @@ ms.reviewer:
14
14
## SYNOPSIS
15
15
This cmdlet is available only in the cloud-based service.
16
16
17
-
Use the New-AvailabilityConfig cmdlet to create an availability configuration. An availability configuration specifies the Microsoft 365 organizations to exchange free/busy information with.
17
+
Use the New-AvailabilityConfig cmdlet to create the availability configuration that specifies the Microsoft 365 organizations to exchange free/busy information with.
18
18
19
19
For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax).
20
20
@@ -44,7 +44,7 @@ This example creates a new availability configuration to share free/busy informa
44
44
## PARAMETERS
45
45
46
46
### -AllowedTenantIds
47
-
The AllowedTenantIds parameter specifies the tenant ID values of Microsoft 365 organization that you want to share free/busy information with (for example, d6b0a40e-029b-43f2-9852-f3724f68ead9). You can specifiy multiple values separated by commas. A maximum of 25 values are allowed.
47
+
The AllowedTenantIds parameter specifies the tenant ID values of Microsoft 365 organization that you want to share free/busy information with (for example, d6b0a40e-029b-43f2-9852-f3724f68ead9). You can specify multiple values separated by commas. A maximum of 25 values are allowed.
Copy file name to clipboardExpand all lines: exchange/exchange-ps/exchange/Remove-AvailabilityConfig.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -14,7 +14,7 @@ ms.reviewer:
14
14
## SYNOPSIS
15
15
This cmdlet is available only in the cloud-based service.
16
16
17
-
Use the Remove-AvailabilityConfig cmdlet to remove an availability configuration. An availability configuration specifies an existing account that's used to exchange free/busy information between organizations.
17
+
Use the Remove-AvailabilityConfig cmdlet to remove the availability configuration that specifies the Microsoft 365 organizations to exchange free/busy information with.
18
18
19
19
For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax).
20
20
@@ -42,7 +42,7 @@ This example removes the existing availability configuration.
42
42
## PARAMETERS
43
43
44
44
### -Identity
45
-
The Identity parameter specifies the availability configuration that you want to remove. The default name of the availability configuration you create by using the New-AvailabilityConfig is Availability Configuration.
45
+
The Identity parameter specifies the availability configuration that you want to remove. You don't need to use this parameter, because there's only one availability configuration object named Availability Configuration in any organization.
This example is useful with a trusted cross-forest Availability service. If the remote forest is trusted, and a per-user free/busy proxy account or group in the remote forest is configured to use the service account, the configuration is added to the current forest to authorize the Microsoft ActiveSync request from the remote forest.
50
+
In on-premises Exchange, this example is useful with a trusted cross-forest Availability service. If the remote forest is trusted, and a per-user free/busy proxy account or group in the remote forest is configured to use the service account, the configuration is added to the current forest to authorize the Microsoft ActiveSync request from the remote forest.
This example is useful if the remote forest isn't trusted. Because this account is used for a cross-forest free/busy proxy account or group, minimize security vulnerabilities by using the credentials of a user who doesn't have an Exchange mailbox. When you're prompted, type the username and password.
57
+
In on-premises Exchange, this example is useful if the remote forest isn't trusted. Because this account is used for a cross-forest free/busy proxy account or group, minimize security vulnerabilities by using the credentials of a user who doesn't have an Exchange mailbox. When you're prompted, type the username and password.
In this example for Exchange Online, the availability config is modified to allow free/busy sharing only with the specified tenants.
64
+
In Exchange Online, this example allows free/busy sharing only with the specified tenants.
65
65
66
66
## PARAMETERS
67
67
68
68
### -AllowedTenantIds
69
69
This parameter is available only in the cloud-based service.
70
70
71
-
The AllowedTenantIds parameter specifies the tenant ID values of Microsoft 365 organization that you want to share free/busy information with (for example, d6b0a40e-029b-43f2-9852-f3724f68ead9). You can specifiy multiple values separated by commas. A maximum of 25 values are allowed.
71
+
The AllowedTenantIds parameter specifies the tenant ID values of Microsoft 365 organization that you want to share free/busy information with (for example, d6b0a40e-029b-43f2-9852-f3724f68ead9). You can specify multiple values separated by commas. A maximum of 25 values are allowed.
72
72
73
73
To replace all existing tenant IDs with the values you specify, use the following syntax: `"TenantID1","TenantID2",..."TenantID25"`.
This parameter is functional only in on-premises Exchange.
129
+
128
130
The OrgWideAccount parameter specifies who has permission to issue proxy Availability service requests on an organization-wide basis. You can specify the following types of users or groups (security principals) for this parameter:
129
131
130
132
- Mailbox users
@@ -162,6 +164,19 @@ This parameter is available only in on-premises Exchange.
162
164
163
165
The PerUserAccount parameter specifies an account or security group that has permission to issue proxy Availability service requests on a per-user basis.
164
166
167
+
You can use any value that uniquely identifies the user or group. For example:
0 commit comments