Set-CsTeamsEventsPolicy
This cmdlet allows you to configure options for customizing Teams events experiences. Note that this policy is currently still in preview.
Syntax
Set-CsTeamsEventsPolicy
[-AllowWebinars <String>]
[-EventAccessType <String>]
[-AllowTownhalls <String>]
[-AllowEmailEditing <String>]
[-AllowedQuestionTypesInRegistrationForm <String>]
[-AllowEventIntegrations <Boolean>]
[-AllowedWebinarTypesForRecordingPublish <String>]
[-AllowedTownhallTypesForRecordingPublish <String>]
[-TownhallChatExperience <String>]
[-Description <String>]
[-UseMicrosoftECDN <Boolean>]
[-Identity] <String>
[-Force]
[-WhatIf]
[-Confirm]
[<CommonParameters>]
Description
User-level policy for tenant admin to configure options for customizing Teams events experiences. Use this cmdlet to update an existing policy.
Examples
Example 1
Set-CsTeamsEventsPolicy -Identity Global -AllowWebinars Disabled
The command shown in Example 1 sets the value of the Default (Global) Events Policy in the organization to disable webinars, and leaves all other parameters the same.
Parameters
-AllowedQuestionTypesInRegistrationForm
This setting governs which users in a tenant can add which registration form questions to an event registration page for attendees to answer when registering for the event.
Possible values are: DefaultOnly, DefaultAndPredefinedOnly, AllQuestions.
Type: | String |
Position: | Named |
Default value: | None |
Required: | False |
Accept pipeline input: | False |
Accept wildcard characters: | False |
-AllowedTownhallTypesForRecordingPublish
This setting describes how IT admins can control which types of Town Hall attendees can have their recordings published.
Possible values are: None, InviteOnly, EveryoneInCompanyIncludingGuests, Everyone.
Type: | String |
Position: | Named |
Default value: | None |
Required: | False |
Accept pipeline input: | False |
Accept wildcard characters: | False |
-AllowedWebinarTypesForRecordingPublish
This setting describes how IT admins can control which types of webinar attendees can have their recordings published.
Possible values are: None, InviteOnly, EveryoneInCompanyIncludingGuests, Everyone.
Type: | String |
Position: | Named |
Default value: | None |
Required: | False |
Accept pipeline input: | False |
Accept wildcard characters: | False |
-AllowEmailEditing
This setting governs if a user is allowed to edit the communication emails in Teams Town Hall or Teams Webinar events. Possible values are:
- Enabled: Enables editing of communication emails.
- Disabled: Disables editing of communication emails.
Type: | String |
Position: | Named |
Default value: | None |
Required: | False |
Accept pipeline input: | False |
Accept wildcard characters: | False |
-AllowEventIntegrations
This setting governs access to the integrations tab in the event creation workflow.
Possible values true, false.
Type: | Boolean |
Position: | Named |
Default value: | None |
Required: | False |
Accept pipeline input: | False |
Accept wildcard characters: | False |
-AllowTownhalls
This setting governs if a user can create town halls using Teams Events. Possible values are:
- Enabled: Enables creating town halls.
- Disabled: Disables creating town halls.
Type: | String |
Position: | Named |
Default value: | None |
Required: | False |
Accept pipeline input: | False |
Accept wildcard characters: | False |
-AllowWebinars
This setting governs if a user can create webinars using Teams Events. Possible values are:
- Enabled: Enables creating webinars.
- Disabled: Disables creating webinars.
Type: | String |
Position: | Named |
Default value: | None |
Required: | False |
Accept pipeline input: | False |
Accept wildcard characters: | False |
-Confirm
The Confirm switch does not work with this cmdlet.
Type: | SwitchParameter |
Aliases: | cf |
Position: | Named |
Default value: | None |
Required: | False |
Accept pipeline input: | False |
Accept wildcard characters: | False |
-Description
Enables administrators to provide explanatory text to accompany a Teams Events policy.
Type: | String |
Position: | Named |
Default value: | None |
Required: | False |
Accept pipeline input: | False |
Accept wildcard characters: | False |
-EventAccessType
This setting governs which users can access the event registration page or the event site to register. It also governs which user type is allowed to join the session/s in the event. Possible values are:
- Everyone: Enables creating events to allow in-tenant, guests, federated, and anonymous (external to the tenant) users to register and join the event.
- EveryoneInCompanyExcludingGuests: Enables creating events to allow only in-tenant users to register and join the event.
Type: | String |
Position: | Named |
Default value: | None |
Required: | False |
Accept pipeline input: | False |
Accept wildcard characters: | False |
-Identity
Unique identifier assigned to the Teams Events policy.
Type: | String |
Position: | 1 |
Default value: | None |
Required: | False |
Accept pipeline input: | False |
Accept wildcard characters: | False |
-TownhallChatExperience
This setting governs whether the user can enable the Comment Stream chat experience for Town Halls.
Possible values are: Optimized, None.
Type: | String |
Position: | Named |
Default value: | None |
Required: | False |
Accept pipeline input: | False |
Accept wildcard characters: | False |
-UseMicrosoftECDN
This setting governs whether the global admin disables this property and prevents the organizers from creating town halls that use Microsoft eCDN even though they have been assigned a Teams Premium license.
Type: | Boolean |
Position: | Named |
Default value: | None |
Required: | False |
Accept pipeline input: | False |
Accept wildcard characters: | False |
-WhatIf
The WhatIf switch does not work with this cmdlet. The cmdlet is not run.
Type: | SwitchParameter |
Aliases: | wi |
Position: | Named |
Default value: | None |
Required: | False |
Accept pipeline input: | False |
Accept wildcard characters: | False |
Inputs
None
Outputs
System.Object
Comentários
https://aka.ms/ContentUserFeedback.
Em breve: Ao longo de 2024, eliminaremos os problemas do GitHub como o mecanismo de comentários para conteúdo e o substituiremos por um novo sistema de comentários. Para obter mais informações, consulteEnviar e exibir comentários de