Skype for Business Topology Support with Office 365, Cloud Connector Edition, Cloud PBX and PSTN Calling

-
Topology support in Office 365 with Skype for Business


A frequently asked question is the support for the different topologies. Later in this document I also provide a generic overview about a possible migration path towards one or the other topology.


The rudimentary described supported topologies are the ONLY possible setups.

There is not possible and supported way in combining any of those topologies!


On-Premise without any Office 365 connectivity


This is typically a solution, where you don’t own an Office 365 “E” Plan. Therefore, you are not entitled using any of the Office 365 features. Same is valid, if you own only an Exchange Online Plan, whereby none of the Skype for Business Online Services are subject to be used.
 

On-Premise with Office 365 connectivity (Federation to Office 365 and Cloud PBX and PSTN CALLING SERVICE)


This is the only scenario, where users are hosted either in Office 365 and some users stay SfB enabled On-Premise. Meaning you have a mixed environment.
This is the only mixed scenario, where local PSTN breakouts with your On-Premise Skype for Business enabled users and the other users enabled on Office 365 (which MUST use PSTN Calling Service or the local PSTN breakouts) are combined. It is not possible for Online user to be mixed for PSTN Calling Service and PSTN local breakout on-premise. This is technical limitation due to Voice Routes in the Office 365 environment.
Note:
A PSTN Calling Service is subject to the regional availability in the country where you required PSTN Calling.
USER LOCATION
PSTN breakout
Users enabled with SfB On-Premise
MUST be On-Premise with local PSTN Gateway
Users enabled with SfB Online in Office 365 (either or option)
PSTN Calling Service in Office 365 -> Calling Plan
On-Premise PSTN breakout with local Gateway -> CloudPBX

Advanced Voice Features (e.g. Response Group or Group Call Pickup)

In case any user requires Advanced Calling Feature, this user must be enabled for On-Premise Skype for Business.

Note:
In later updates, Microsoft will successively add more features to the Office 365 environment, making is obsolete running On-Premise installations.

Office 365 with CCE (Cloud PBX)


If e.g. the PSTN Calling Service isn’t available, or you required On-Premise PSTN connectivity (e.g. for Contact Centers) you can move all users into Office 365 and utilize the Cloud PBX feature in combination with Cloud Connector Edition.

With CCE you can mix online users with CCE On-Premise Voice PSTN breakout and Microsoft Calling Service.

Explicitly, CCE CANNOT be used with Skype for Business On-Premise Topology!


Office 365 with PSTN Calling Service (native Calling Plan)


If you don’t need either advanced calling features or any PSTN On-Premise connectivity, you can move all users into Office 365.


Author:

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 modif...
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, uniqu...
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