Set-CsTeamInteropPolicy (do not exists)

-

Upgrade Journey to TEAMS


MyAdvisor:
https://myadvisor.fasttrack.microsoft.com/CloudVoice/Guidance
or
https://myadvisor.fasttrack.microsoft.com/

The cmdlet Set-CsTeamsInteropPolicy has never existed. Previously, if you wanted to create a new custom Teams Interop policy you would have to use the New-CsTeamsInteropPolicy. But now also the New-CsTeamsInteropPolicy cmdlet has been deprecated and it is not possible to create custom Teams Interop Policies anymore. Additionally, Microsoft is in the process of retiring TeamsInteropPolicy and you need to use the pre-canned instances moving forward:

• DisallowOverrideCallingDefaultChatDefault
• DisallowOverrideCallingSfbChatSfb
• DisallowOverrideCallingTeamsChatTeams

Here the answer from Microsoft with a similar question about custom Teams Interop policies:

"There is no need to create a new instance of TeamsInteropPolicy. All the necessary instances are already created. Also, we are retiring TeamsInteropPolicy and at this point only 3 instances of TeamsInteropPolicy are supported to be granted.

• DisallowOverrideCallingDefaultChatDefault
• DisallowOverrideCallingSfbChatSfb
• DisallowOverrideCallingTeamsChatTeams

Going forward TeamsUpgradePolicy replaces TeamsInteropPolicy. 
During the transition, customers should set both InteropPolicy and UpgradePolicy."

You can see these answers I got, at the comments and questions section at the very end of this article: https://docs.microsoft.com/en-us/microsoftteams/configuring-teams-calling-quickstartguide 

NOTE:

Therefore, remember you will NOT be able to use Set-TeamsUpgradePolicy, after your tenant was "migrated". So Teams has become your only collab tool


EXAMPLES


Example 1: Grant Policy to an individual user


PS C:\> Grant-CsTeamsUpgradePolicy -PolicyName UpgradeToTeams -Identity mike@domain.com
The above cmdlet assigns the "UpgradeToTeams" policy to user Mike@domain.com. This effectively upgrades the user to Teams only mode.

Example 2: Grant Policy to the entire tenant

PS C:\> Grant-CsTeamsUpgradePolicy -PolicyName SfBOnly
To grant a policy to all users in the org (except any that have an explicit policy assigned), omit the identity parameter.

Comments

Post a Comment

Popular posts from this blog

How to hide users from GAL if they are AD Connect synchronized

-
Image
How to hide and un-hide users from Global Address List (GAL) in Exchange Online if they are AD Connect synchronized Hiding User from GAL isn't possible if those are synchronized form On-Premises Active Directory. The local AD is the leading system for all important attributes, like SMTP, UPN and hiding from GAL. Especially during a cross-tenant migration, you do not want to see not migrated user in the GAL. Those User aren't actively working until their cut-over day. Since the Exchange Online attribute  msExchHideFromAddressList s is an AD on-premises parameter, we have two possible ways hiding user in BME from GAL.   Modify the AD Connect for your teant with a custom rule, by using a extensionAttribute to set the HidefromGAL. In this rule, for users which have an entry in the extensionAttribute, hiding / un-hiding will be controlled by AD Connect This is the best option for Cross-Tenant Migration, if you run 2 or more AD Connect system We direct modify the AD hide at
Read more

Cannot join external Lync Meeting: Lync Edge Server Single IP Address (Lync Edge Server Single IP Web Conferenceing Problem)

-
Image
Lync Edge Server FQDN and IP PORTS (Version 1.2, Update 26.11.2014) As we all know, we can configure Lync Edge Server in several way. 1) Single Edge Server with a SINGLE IP ADDRESS 2) Single Edge Server with MULTIPLE IP ADDRESSES (3x IPs) 3) Multiple Edge Server in a Pool, with MULTIPLE IP ADDRESSES (Zx 3 IPs) Regardless what we are going to configure, there are common / well-known TCP Port necessary making Lync work, which are: Access: Port: 443 and 5061 Conferencing: Port: 443 and (444) AV: Port: 443 (I have not listed other ports, e.g. STUN or the dynamic port range. This is not required for the topic discussed here) External FQDN with single IP address: What can we see here? If we are going to choose a single IP address, we would have TCP Port overlapping. Therefore the only way avoiding this is assigning other ports. Additionally we will also see and are reminded that Lync highly depends on DNS. If we have single IP, we must have use single, unique FQDN fo
Read more

MFA with Guest Access and different tenants settings

-
Image
There is an update regarding MFA Multi Factor Authentication. If you are guest with a different Tenant, the MFA Settings are now reflecting the settings of all tenants in a different way. Each MFA setting is reflected and you can setup your MFA device as per tenant and the admin settings allow. Login to your Profile in Office 365/ Azure AD: https://account.activedirectory.windowsazure.com/r/#/profile or https://myapps.microsoft.com Go to your PROFILE: Sign in to https://myapps.microsoft.com Select your account name in the top right, then select profile. Select Additional security verification. If might be happen, your admin hast configured MFA, so you wouldn't see this menu. Simply switch the tenant to the guest tenant where you need to configure MFA. Once you go back to your profile and you will find the MFA device and other settings a usual:
Read more