Get-CsTeamsVirtualAppointmentsPolicy
This cmdlet is used to fetch policy instances of TeamsVirtualAppointmentsPolicy.
Syntax
Get-CsTeamsVirtualAppointmentsPolicy
[[-Identity] <String>]
[<CommonParameters>]
Get-CsTeamsVirtualAppointmentsPolicy
[-Filter <String>]
[<CommonParameters>]
Description
Fetches instances of TeamsVirtualAppointmentsPolicy. Each policy object contains a property called EnableSmsNotifications
. This property specifies whether your users can choose to send SMS text notifications to external guests in meetings that they schedule using a virtual appointment meeting template.
Examples
Example 1
PS C:\> Get-CsTeamsVirtualAppointmentsPolicy
Identity EnableSmsNotifications
-------- ----------------------
Global True
Tag:sms-enabled True
Tag:sms-disabled False
Fetches all the policy instances currently available.
Example 2
PS C:\> Get-CsTeamsVirtualAppointmentsPolicy -Identity sms-enabled
Identity EnableSmsNotifications
-------- ----------------------
Tag:sms-enabled True
Fetches an instance of a policy with a known identity.
Example 3
PS C:\> Get-CsTeamsVirtualAppointmentsPolicy -Filter *sms*
Identity EnableSmsNotifications
-------- ----------------------
Tag:sms-enabled True
Tag:sms-disabled False
The Filter
parameter can be used to fetch policy instances based on partial matches on Identity.
Note: The "Tag:" prefix can be ignored when specifying the identity.
Parameters
-Filter
This parameter can be used to fetch policy instances based on partial matches on the Identity field.
Type: | String |
Position: | Named |
Default value: | None |
Required: | False |
Accept pipeline input: | False |
Accept wildcard characters: | False |
-Identity
This parameter can be used to fetch a specific instance of the policy.
Type: | String |
Position: | 1 |
Default value: | None |
Required: | False |
Accept pipeline input: | False |
Accept wildcard characters: | False |
Inputs
System.String
Outputs
TeamsVirtualAppointmentsPolicy.Cmdlets.TeamsVirtualAppointmentsPolicy
Related Links
Commentaires
https://aka.ms/ContentUserFeedback.
Bientôt disponible : Tout au long de 2024, nous allons supprimer progressivement GitHub Issues comme mécanisme de commentaires pour le contenu et le remplacer par un nouveau système de commentaires. Pour plus d’informations, consultezEnvoyer et afficher des commentaires pour