Merge pull request #11538 from TariqSharif-MSFT/patch-1

Update New-AvailabilityConfig.md

Author: chrisda

exchange/exchange-ps/exchange/New-AvailabilityConfig.md

@@ -14,16 +14,17 @@ ms.reviewer:
 ## SYNOPSIS
 This cmdlet is available only in the cloud-based service.
 
-Use the New-AvailabilityConfig cmdlet to create an availability configuration. An availability configuration specifies an existing account that's used to exchange free/busy information between organizations.
+Use the New-AvailabilityConfig cmdlet to create an availability configuration. An availability configuration specifies the Microsoft 365 organizations to exchange free/busy information with. 
 
 For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax).
 
 ## SYNTAX
 
 ```
-New-AvailabilityConfig -OrgWideAccount <SecurityPrincipalIdParameter>
+New-AvailabilityConfig 
  [-AllowedTenantIds <MultiValuedProperty>]
  [-Confirm]
+ [-OrgWideAccount <SecurityPrincipalIdParameter>]
  [-WhatIf]
  [<CommonParameters>]
 ```
@@ -35,53 +36,39 @@ You need to be assigned permissions before you can run this cmdlet. Although thi
 
 ### Example 1
 ```powershell
-New-AvailabilityConfig -OrgWideAccount "Tony Smith"
+New-AvailabilityConfig -AllowedTenantIds "d6b0a40e-029b-43f2-9852-f3724f68ead9","87d5bade-cefc-4067-a221-794aea71922d"
 ```
 
-This example creates a new availability configuration. The existing account named Tony Smith will be used to exchange free/busy information between organizations.
+This example creates a new availability configuration to share free/busy information with the specified Microsoft 365 organizations.
 
 ## PARAMETERS
 
-### -OrgWideAccount
-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:
-
-- Mailbox users
-- Mail users with a Microsoft account
-- Security groups
-
-You can use any value that uniquely identifies the user or group. For example:
-
-- Name
-- Alias
-- Distinguished name (DN)
-- Canonical DN
-- Domain\\Username
-- Email address
-- GUID
-- LegacyExchangeDN
-- SamAccountName
-- User ID or user principal name (UPN)
+### -AllowedTenantIds
+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.
 
 ```yaml
-Type: SecurityPrincipalIdParameter
+Type: MultiValuedProperty
 Parameter Sets: (All)
 Aliases:
 Applicable: Exchange Online
 
-Required: True
+Required: False
 Position: Named
 Default value: None
 Accept pipeline input: False
 Accept wildcard characters: False
 ```
 
-### -AllowedTenantIds
-{{ Fill AllowedTenantIds Description }}
+### -Confirm
+The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
+
+- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`.
+- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding.
 
 ```yaml
-Type: MultiValuedProperty
+Type: SwitchParameter
 Parameter Sets: (All)
-Aliases:
+Aliases: cf
 Applicable: Exchange Online
 
 Required: False
@@ -91,16 +78,13 @@ Accept pipeline input: False
 Accept wildcard characters: False
 ```
 
-### -Confirm
-The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
-
-- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`.
-- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding.
+### -OrgWideAccount
+This parameter is reserved for internal Microsoft use.
 
 ```yaml
-Type: SwitchParameter
+Type: SecurityPrincipalIdParameter
 Parameter Sets: (All)
-Aliases: cf
+Aliases:
 Applicable: Exchange Online
 
 Required: False