Skype Academy presents: Hybrid and Online Migration Summary

Recently some new videos were published to the Skype Academy training and one i think a lot of people will be interested in is Skype for Business Hybrid and SfB Online Migrations. A list of the new videos available is here

This video covers all aspects of Hybrid at a high level including

  • Lync / SfB Server Topology requirements
  • Identity Requirement
  • AAD Connect ADFS
  • High Level Network and Firewall Information
  • Managing and configuring Hybrid
  • Also some troubleshooting scenarios
  • Links to Skype operations Framework as well

Definitely worth a watch

Also definitely worth a read is Josh Blalocks Hybrid Handbook download here

Below is a summary of the Skype for Business Academy video here.


This is the January 2017 version of this training.

This content is subject to change as with all Cloud technology information and training.


There’s a lot to cover and the video is around 45mins long. It great this video doesn’t just cover Lync / SfB it also talks over identity AAD Connect and ADFS


Skype Operations Framework (SOF)

With Hybrid this fits into Cloud Migration as customer may be looking to migrate from on premises to online and also customers may require to keep and have users homed on premises and online due to functionality not being available online.


For Hybrid we are looking a Cloud Migration workflow of the SOF. Recommend you take out SOF and the great download and assets that are available here. To Quickly get started use the Quick Start on the home page.

Goal of Hybrid

Is to have a shared SIP namespace  Online and On premise. Where you can have users home on premises and online using the same SIP address space. This allows customer to move users between on premises and online and back from online to on premises and also provides a migration method from on premises to online which also migrates existing contacts, then allows the on premises environment to be decommissioned once all services and users have moved.

You could look at a hard cut over if you wanted to move to Online only but you would lose existing contacts and the experience is not as seamless. I would recommend hybrid if possible.

For example is available on premise and online.


Hybrid Benefits


  • Move users from On premise to Online and also you can move from online to on premises.
  • Allows user to leverage CLOUD only features and functionality such as Skype meeting broadcasts and Cloud PBX.
  • GET the best of both worlds ! Users on premise can leverage full enterprise voice functionality.

Topology Requirements for Hybrid


Full server deployment on premises and Administrator tools of the following:

  • Skype for Business Server 2015
  • Lync Server 2013
  • Lync Server 2010

Please note the latest Cumulative updates are always recommended.

Please note for Cloud PBX with on premises PSTN connectivity you require SfB Server 2015 or Lync Server 2013. Lync Server 2010 is not supported.

Lync Server 2013 – Support Cloud PBX

Lync Server 2010 – DOES NOT support Cloud PBX

Allowing for Mixed Topologies



You can have a mix of Skype for Business Server and Lync Server but note the requirements above.

Certain roles need to be Skype for Business 2015.

For more detailed information please refer to TechNet here

CLOUD PBX with On premises PSTN connectivity Hybrid requirements

Must be SfB Server or Lync Server 2013.

Please note for Cloud PBX you need to have the following server roles with the supported versions


Office 365 and Identity Requirements

Identity is Key and in alot of cases customers already have this deployed if they have Exchange Online for example. If new to Office 365 this is a key requirement.


Also consider Interop with Exchange and Networking Requirements


Skype for Business Edge Connectivity

HA and DR is key on premises as sign in is pointed to on premises servers

If you want Outlook web access integration you must have your mailbox homed Online.

Azure voicemail can also utilise on premises exchange if required.

Networking – Need to open ports on firewall.

Please check Office 365 IP and Ports here

Please check bandwidth requirements as well as traffic will go over the internet to SfB Online. Please check out Skype for Business bandwidth calculator here

MMS Training here

HA and DR Considerations

Hybrid is very very reliant still on the on premises Lync / SfB infrastructure and dont overlook the requirement. All SfB Public DNS records point on premises and are redirect to SfB Online. If clients cant get to the on premises infrastructure then they cant get to SfB online as well.

Please see examples below

The SfB client registration process client does DNS lookup for which resolves to the on premises reverse proxy server NOT SfB Online.


This returns back the internal web services url which redirect the client to SfB Online.


Http Analyse below.

The on premise SfB external web services does a redirect to SfB Online web services



Open all ports for an On premises edge and reverse proxy server deployment and also open port requirements for SfB Online.

On premises Edge Server requirements here

Server Firewall requirements – Server to SfB Online


Always check

SfB Clients to SfB Online  Firewall



Identity Requirements

High level overview only but gives a good overview of Identity requirements for Hybrid. Don’t overlook this requirement.


Identity Management


Authentication and Authorization and definitions above.

Identity Options – Three options for identity with Office 365 only two are suitable with Hybrid.

CLOUD ONLY is NOT an identity option for Hybrid.


  1. Cloud Identity (Not available with Hybrid)
  2. Synchronized Identity (Directory and Password Sync)
  3. Federated Identity (Directory and Federation)

View the differences in Synchronised and Federation including server counts and SSO. Also consider requirements on where authentication will take place.

Password Sync (Synchronized Identity)

AAD Connect only with Password Sync.



Two User IDS but one username and Password

Authentication happens in the CLOUD

Federated Identity

AAD Connect and ADFS and ADFS Web Proxy



True SSO

Higher Server Count

Authentication happens on premises !!! Again reliance on premises infrastructure.

Note password management and resets are on premises.

ADFS 3.0 deployment Options with federation identity

Can be single server but not recommended due to NO high availability.


Recommended to have ADFS server farm deployment for HA an example below.


AAD Connect – Azure Active Directory Connect

How do we sync out user object into Office 365 AAD Connect which was DirSync.



Required for Synchronized and Federated identities.

What does AAD Connect synchronise ?


Not every sync by default. You can use filtering and additional sync features

Common AD sync questions


Licencing of users is seperate

You can still create users in Office 365 but not recommended. Crate on premise and sync up to the Cloud.

How to Deploy Skype for Business Hybrid and Steps required

So we looked at the prereqs now lets see them all. The following prereqs must be in place before you can configure SfB Hybrid.


Please note ALL of the above items must be in place.

Configure AAD Connect


Various tool consolidated into a deployment assistant

AAD Connect – Express Settings


Start with Express and add other options if required.

SfB Enable Federation and Split Domain

Federation must be configured the same on premises and online. IF you use closed federation and have added allowed domain then you these must be added online as well.

he following requirements must be met to successfully configure a hybrid deployment:

  • Domain matching must be configured the same for your on-premises deployment and your Office 365 tenant. If partner discovery is enabled on the on-premises deployment, then open federation must be configured for your online tenant. If partner discovery is not enabled, then closed federation must be configured for your online tenant.

  • The Blocked domains list in the on-premises deployment must exactly match the Blocked domains list for your online tenant.

  • The Allowed domains list in the on-premises deployment must exactly match the Allowed domains list for your online tenant.

  • Federation must be enabled for the external communications for the online tenant, which is configured by using the Skype for Business Online Control Panel.

This is from


This can be done via Management Shell on premises and online



If you have Skype for Business Server you can use the Hybrid Configuration Wizard in SfB Control Panel to configure Hybrid for you via a GUI. This will also run some configuration checks to ensure all prereqs are met for Hybrid.


Please Note the SfB  Front End server do require Internet Access

The Hybrid Control Wizard will do a number of checks to ensure everything is configured before enabling Hybrid.


If it detects an item is not configured it will flag this


After addressing any flagged items run again and


Move Users

Now that the SfB Hybrid is configured its time to move users and we can move them both ways.

BUT before we move them please note

  • User contacts   The limit for contacts for Lync Online users is 250. Any contacts beyond that number will be removed from the user’s contact list when the account is moved to Lync Online.

  • Instant Messaging and Presence   User contact lists, groups, and access control lists (ACLs) are migrated with the user account.

  • Conferencing data, meeting content, and scheduled meetings   This content is not migrated with the user account. Users must reschedule meetings after their accounts are migrated to Lync Online.

Also don’t forget about SOF people !

Remember to refer back to the Skype operations framework


Refer back to the workshop and SOF to ensure you move the correct group of users together.

ALSO KEY to remember user adoption and training, dont skip this in all the excitement.

Before we can move the users we need to determine the migration URL which is a manual process.


Once Migrated URL is determined you can move users.

REMEMBER create users on premises then move Online ! Also key to remember is licence the user in office 365 first otherwise it will error.

What information gets migrated with the users?


Contacts will get migrated but note there’s a 250 contact limit in SfB Online so you need to make sure you don’t have more than 250 contacts otherwise only the first 250 will be migrated.

For Meeting if you mailbox is in Exchange Online you can utilise the new Meeting Migration Service to update existing scheduled meeting URLs.

If your mailbox is in Exchange on premises then there is a Meeting Migration Tool that you can download and install on each users computer that will run and search the user mailbox for scheduled meetings and update the URL and send updated meeting invites to meeting attendees with the new meeting details. MMS does all this as well but its an automated service if your mailbox is online only. Sorry on prem exchange people.

Also note users will now have to use SfB Online policies to your online.

Also note client supportability and On premises SfB / Lync policies are not carried over to online.

  • Client support    Some users may require a new client version when they are moved to Skype for Business Online. For Office Communications Server 2007 R2, users must be moved to a Skype for Business Server or Lync Server 2013 pool prior to migration to Skype for Business Online.

  • On-premises policies and configuration (non-user)   Online and on-premises policies require separate configuration. You cannot set global policies that apply to both


Moving users back to On premises

Perhaps there are features that are only available on premises that are not available in online.



What happens to AD user attributes ?

When enabling for SfB online and on premises.



On premises users need to be ware of online users


SfB Online user NOT enabled for SfB. No attributes set.




Moving Online user to on premises



Attributes populated for on premises details

Manage SFB

Next we look at management of users, moving from Control Panel and searching for users online.



In control panel you can search for online users only using the filter

Also you can use PowerShell


Online users you can modify some option not all.


Here you can move the user.


Front End Server needs internet access to move users


Error Example – You must licence user online for SfB

Move to on premise example




CQD – Call Quality Dashboard

Good tool for checking call quality please note there is an on premises CQD and CQD Online. Theses are separate dashboards.


More details on CQD here

CQD training here

Troubleshooting Scenarios


Cant sign into SfB Control Panel for Hybrid Configuration Wizard

Issue above if due to Front End Server not having Internet Access










Client Support

This isn’t referenced in the video but is important to note

The following clients are supported with Skype for Business Online in a hybrid deployment:

  • Skype for Business

  • Lync 2013

  • Lync 2010

  • Lync Windows Store app

  • Lync Web App

  • Lync Mobile

  • Lync for Mac 2011

  • Lync Room System and Skype for Business Room System

  • Lync Basic 2013

  • Microsoft Surface Hub



Skype for Business Server 2015 February 2017 Cumulative Update

Happy valentines ! I Noticed last night on twitter thanks to @Luca_Vitali that a new Cumulative update was released yesterday for Skype for Business Server and there a lot in this one Smile !

Windows Server 2016 is mentioned which is great and cant be long for this to be a supported OS for SfB Server now. I did check TechNet for SfB OS’s and 2016 isn’t listed yet. Also it again notes an E911 fix for non windows auth clients so this may be critical update again. There seems to be have been a few E911 bugs recently.


  • Fix for SfB Installer on Server 2016 ! So it wont be long now people !
  • E911 fix for non windows auth clients
  • Push notification support for iOS and Android
  • Presence and contact card updates
  • Skype web sdk update for accepting across-domain anonymous meeting join requests

It also noted that This update enables Location-Based Routing to support the Skype for Business mobile clients which is interesting.

Version Number for this update – 9319.277

Lets dig into some details.

Skype for Business Server CU5 details

This update enables Location-Based Routing to support the Skype for Business mobile clients. It also fixes the following issues

Improvements and fixes in the February 2017 update
Fix and Improvement Symptom / Cause
  • 3212371 Skype for Business Server 2015 installer can’t update necessary drivers (Media Relay driver)

Microsoft Skype for Business Server 2015 installer may not update necessary drivers for Skype for Business Server 2015. For example, the Media Relay driver that’s used by Skype for Business Server 2015 may not be updated silently, and some known issues cannot be fixed after you install certain updates. Meanwhile, you may find the version of the RTCMrDrv.sys file in the following location is 5.0.8308.241:

%WINDIR%\system32\drivers directory

This issue occurs in the following scenario: 

You have installed cumulative update 6.0.9319.249 for Skype for Business Server 2015. Meanwhile, you have installed any cumulative update after the cumulative update 6.0.9319.249 for Skype for Business Server 2015 after you install the cumulative update 6.0.9319.249.

3209571 LastActive attribute provides inaccurate information about a user’s presence status in Skype for Business The LastActive attribute provides inaccurate information (for example, offline for 180 days) about a contact’s presence status in a Microsoft Skype for Business server 2015 environment. This issue occurs because of data loss after a user is moved from one pool to another pool. See KB3056287 for more information about the same issue in Skype for Business Online. This issue also occurs after you are re-homed on another Front End server in a same pool. For example, this issue occurs after a server patching.
3209570 You can’t set mobile phone number if it matches work phone number in Skype for Business Server 2015 Assume that you disable the Call Via Work feature in mobility policy and set your work phone number and mobile phone number to the same number in a Microsoft Skype for Business Server 2015 environment. In this situation, you can’t set the same mobile phone number in Skype for Business mobile app.
3209569 Display name in contact cards is not returned in Skype for Business Server 2015 When you search for a contact in Microsoft Skype for Business Server 2015, display name of the contact isn’t shown in the search result .
3209568 Add Push Notification support for Skype for Business for iOS and Android clients in Skype for Business Server 2015 To enable this feature in a Microsoft Skype for Business Server 2015 environment, install the February 2017 cumulative update 6.0.9319.277 for Skype for Business Server 2015.
3209567 Add a flag to the Web.config file to allow Join Launcher to accept across-domain anonymous meeting join requests This update adds a flag (allowCrossDomainRequests="true") to the Web.config file in Microsoft Skype for Business Server 2015 to allow the Join Launcher feature to accept anonymous meeting join requests that are across-domain from the Web SDK.
3209566 Skype for Business Server 2015 installer may fail silently in Windows Server 2016 Microsoft Skype for Business Server 2015 installer may be unsuccessful in Windows Server 2016.
3209565 Enhanced 911 (E911) calls don’t work through the non-Windows authentication in Skype for Business E911 calls don’t work when the non-Windows authentication is used to authenticate the Microsoft Skype for Business server.
3209563 Update reverts the Application Sharing Server (ASMCU) changes in CU4 in Skype for Business Server 2015 You receive a RTP and RCTP musing issue after you upgrade the version of Microsoft Skype for Business Server 2015 to cumulative update 4 (CU4).
3207037 UCWA may crash when parsing the ms-trunking-peer header in Skype for Business Server 2015 Unified Communications Web API (UCWA) crashes because of an invalid value in the ms-trunking-peer header in Skype for Business Server 2015.

There seems to be quite a few components are require updating



There doesn’t seem to be any database updates required with this CU buts its always worth checking using test-csdatabase.

Post Feb 2017 CU Install

DatabaseName  ExpectedVersion InstalledVersion
rtcxds 15.13.10 15.13.10
rtcshared 5.0.1 5.0.1
rtcab 62.42.12 62.42.12
rgsconfig 5.5.1 5.5.1
rgsdyn 2.2.1 2.2.1
cpsdyn 1.1.2 1.1.2
xds 10.15.4 10.15.4
lis 3.3.1 3.3.1
mgc 1.42.1 1.42.1

Download Link


Skype for Business Broadcast – VMware & VDI in SfB Summary

Last Friday Feb 10th 2017 there was a Skype meeting broadcast from Microsoft on VMware and VDI.

Link to Broadcast

Below is summary and run through of the broadcast. May be useful if you don’t get change to watch the recording above.

Paul Kennan from Microsoft presents


Joining Microsoft was VMware Tony Wim director of Product Management


Microsoft a valued partner and VMware see the adoption of SfB growing and growing !

Broadcast shows preview feature via federation between VMware and Microsoft


SfB very important to VMware, VMware use SfB daily to communicate and collaborate so critical to their business.


VMware’s virtual desktop offering VMware horizon is growing with multiple industries using this.

  • 75-80% of VMware customer using either Lync or SfB
  • 3 Billion of calls per day running in Skype ecosystem
  • 3 Trillion minutes of video
  • Microsoft states they are number 1 meeting provider

Options to deliver SfB via VDI


VMware partnership with Microsoft goes back to 2012 / 2013 VMware seeing big adoption of Lync 2013 at this time. VMware worked with Microsoft in 2013 with Horizon view desktop and the Lync VDI client.

Audio and Video calls through horizon view desktop via the Lync VDI plugin shown in first column. Lync VDI plugin support Lync Server 2013 and SfB Server 2015. NO SFB Online support. Only supports windows thin clients

With Real time audio and video, a lot of customer use this to try and support audio and video in Linux or mac clients. Not supported and has media hair pinning, no benefit of the Lync VDI plugin. Customer still wanted to do this regardless. SfB was critical to customers and they would do it any way they could knowing the risks.

Last year VMware announced partnership for SfB as of Q1 2017 the VMware virtualization pack will be available. It will support Lync Serer 2013, SfB Server 2015 and support for SfB Online / Office 365. Future Plans for Office 365.

The Tech preview will be Lync / SfB Server and SfB 2015 client only at this time.

More about tech preview



~Shown at VMware Barcelona last year and was part of keynote

Demo SfB Call in horizon view desktop with audio and video inside VMware View Desktop

Optimized solution without negatively affecting VMware back end server infrastructure

VMWARE seeing huge interest of when this will be available.

High Level overview of Horizon UC Virtualization Pack


You have client endpoint (Machine) which connects to Virtual Machine (Desktop)

In the middle is virtual machine (Virtual desktop) which has Installed the SfB Client

On client machine at bottom has horizon client which accesses and remotes to the virtual desktop

Two new components

  • Horizon media proxy – inside virtual desktop
  • Horizon media engine – client endpoint


User uses horizon client to connect to virtual desktop, they launch SfB client, over the virtual channels, the media engine will pair with media proxy and session will run in optimised mode.

You use SfB client and have an AV call, the minute it start the media engine takes over and processes all the audio and video, installed on the client endpoint so this is where the media processing takes place not on the infrastructure. RP Media processing is offloaded.

Media also goes direct P2P (endpoint to endpoint) and NOT on the back end server infrastructure.

Most optimized architecture VMware mentions

Key Benefits


  • Allows Partners to communicate and collaborate without negative impacts to servers
  • HD quality
  • Point to Point media delivery – QoS will be honoured on network
  • Native Skype codecs, same bandwidth as standard SfB media.

With VMware on-board this gives Microsoft more coverage and supportability in scenarios for SfB. Organizations have more options. All major platforms will have more support moving forward.

Key Capabilities of SfB Client

Some features require the media engine and some don’t, the below show which are required.


New optimized solution enables two things


If you don’t use Audio or Video you don’t need the media engine deployed.

Tech Preview Info and features available.


  • Media Engine for Windows clients only
  • Point to Point Audio and Video
  • Connections with Lync Server 2013 and Skype for Business Server 2015.
  • Office 365 not supported yet but support in the future
  • Only supporting SfB 2015 Client NOT SfB 2016 but will be looked to be supported at a later date.
  • PSTN calls
  • Remote connectivity via Edge server

Meetings not mentioned here.

Preview Requirements

Microsoft and VMware requirements


Microsoft Lync Server 2013 / SfB Server and SfB 2015 client.

VMware requirement is 7.1 and new Horizon client believed to be 4.4  client.

How to gain access to UC Virtualization pack ?


Made available as separate downloads

Question and Answers in broadcast from audience


When will 7.1 be released ?

Tech Preview – end of Q1 of 2017 could be up to end of march.

GA will come later following tech preview


Will be the new VMware V Pack make the Lync VDI not required ?

Its an evolution of Lync 2013 VDI plugin but customer want to use Office 365 in the future or Linux or mac clients. These weren’t supported before.

Lync 2013 VDI can still be used for supported environment.


Thin vs zero client supportability ?

Windows thin or Linux thin, media engine supported on both.

VMware new blastextrememe looking to introduce blastzero clients

a lot of options for customers


QoS Support ?

Yes, it will as the RTP Media stream is separate


Will plugin support both PCOIP and RDP ?

NO RDP support


Does plugin break VDI plugin ?

Both 32 and 64 bit of media engine will be available


Does VMware require removal of Lync 2013 VDI thin client ?

VMware not tested having both, from storage perspective you may only want to have one installed at client endpoint.


Will RDSH or published app ?

Only will work in virtual desktop

VMware want to look at supporting published apps


At what level of licencing is required ?

Announced later, no charge for software bit. VMware will announce what additions this will be available in.


Will SfB VDI support gallery view ?

Microsoft requires full version of the client (NOT basic),

Gallery view is not currently supported, VMware looking to support if its possible.


Client version

2015 client supportability only in tech preview, 2016 later, SfB Mac client not supported. Horizon media engine support will come later.


Support for USB tethering ? Such as Polycom CX600 ?

Not currently, looking into at a later timeframe


Does the plug for MMR work ?

USB headset and USB enable in Horizon view is it supported ?

Recommend keeping USB local to the device. Don’t want to redirect USB traffic. Goes against the optimized architecture.


End of Broadcast

No announcement for future broadcast so check Twitter. Should be 2 week from today.

Hope this summary was useful.



Skype for Business Mac Client CU3 February 2017 Update Summary

There been a new Cumulative update 3 released for the Skype for Business Mac Clients. This is February 2017 cumulative update 3 for the SfB Mac Client with some new features and bugs addressed. Thanks to Tom Arbuthnot for tweeting this news last night.

The Feb 2017 cumulative update 3 brings

  • Peer-to-Peer desktop sharing
  • Additional USB Device Support
  • Several other improvements for the client

P2P desktop sharing and more certified usb device support is great and im sure alot of people have been eagerly waiting these features.

More info check out on info on Tech Community here

Manual Download to new Update

You can AutoUpdate or the Manual download link if below. I tried AutoUpdate but it wasn’t showing CU3 version to update to as you can see in screenshots so i manually remove and installed the new version. Suspect the new update will be there soon.

CU3 Update Version Number

With 6th February 2017 update –

Features Added / Bugs

There’s a couple of new features added list above with CU3 and also some bug fixes regarding duplicate contacts, CPU usage when screen sharing and call transfer which are detailed below from Microsoft Tech Community.

Features Added Details

Desktop sharing in P2P Conversations
In our last update, we introduced the capability to share during an audio conversation and promised that we would add sharing for IM/Chat sessions as well.  With this release, we now have included that support, so you can now share during a P2P session for audio and IM.  We hope you find it useful. Please take the time to let us know what scenarios we have enabled for you. Is this for helpdesk? Does it make collaboration frictionless when you can quickly share your screen? Perhaps other scenarios? Let us know.

Additional USB Device Support.
As we get feedback and combine that with telemetry from the client, we note there are some USB devices that are not performing as expected. With this update, we have certified 5 devices and will continue to add devices going forward. That list includes the Polycom CX300, Jabra Speak 510, Jabra Evolve 65, Plantronics Blackwire C520-M and the Logitech Webcam C930e.
Further Improvements / Bug Fixes  

– Customers report duplicate contacts during search

This was related to caching. With this update, impacted customers should take the action to logout out and delete their sign-in information. Sign back in and let us know if that has solved the issue.
– Customers have reported that CPU usage was high during screen sharing
Work has been done and the addition of VBSS viewing should help there. We also expect to add VBSS sharing in a future update which will continue to improve performance.
– In certain scenarios, customers reported issues with call transfer. We have updated this experience to hopefully remove those issues. Please try this out and let us know via the forums if it’s working better for you.

Don’t forget about Known Issues

Its worth reading over these as there’s quite a few ! – Updated 7th Feb 2017

E911 support required SfB Server CU4 or Lync Server 2013 CU8 HF2 – Please make sure you have these updates deployed if you require E-911 services. It does state the below in grey though. Also in known issues it mentions E-911 with ADFS not supported yet.

Important: Users will not be able to dial 911 until the CU4 server update is applied.

Also mentions the requirement for mobility again and the requirements for the latest SfB Servers and Lync Server 2013 CUs if you don’t have mobility enabled.

Other known issues that took my interest are below but there’s alot alot more so please check them out before you get questions and helpdesk tickets.

  • E-911 with ADFS not supported
  • Skype Room Systems cannot join a meeting schedule by Skype for Business on Mac.
  • A Skype for Business on Mac user sometimes sees a blank screen when a Skype for Business on Windows user shares the desktop in an IM conversation (peer-to-peer or group IM).
  • If a user is not logged in to Outlook, presence information in Skype for Business on Mac does not update based on the Outlook calendar.
  • There is a known limitation with Mac search where it will not show federated contacts and Skype consumer contacts; it can only show contacts in the local Active Directory.

More know issues details check them out i recommended it.

How do i update to CU3?

Two methods which are the same as the previous updates.

  • Either using the Microsoft AutoUpdate (MAU) if you have already deployed the SfB Mac client already Smile ( I did try but was showing older version at the time of writing this)
  • Or for new users a manual download via Microsoft download centre here

Do i need to update Lync / SfB Servers ?

For the Feb 2017 CU  the requirements server side are the same as November & January SfB Mac Client Cumulative updates but on the known issues page there are two important things to note, the first around E911 support which is very important and the second the requirement for mobility to be enabled if you don’t have the latest CUs deployed for Lync Server 2013 or SfB Server 2015. Details are below.

  • 911 support requires Skype for Business Server 2015 CU4 (build 9319.272 or higher, now available) or Lync Server 2013 CU8 HF2 (coming soon).

Important: Users will not be able to dial 911 until the CU4 server update is applied.

  • Without Skype for Business Server 2015 CU4 (build 9319.272 or higher, now available) or Lync Server 2013 CU8 HF1 (build 8308.974 or higher, now available), Skype for Business on Mac requires Mobility enablement on the server side. After updating to builds 9317.272 or 8309.973, Mobility enablement will no longer be required.

It does note under the manual download detail that’s its recommended for the best user experience to ensure customers are running the latest Server side cumulative updates which are November 2016 for both SfB and Lync Server 2013. Or it mentions move to Office365 for always up to date infrastructure which made me smile. Downloads link are below.

  • SfB Server 2015 (9319.272) – November 2016 CU4 here
  • Lync Server 2013 (8308.974) – November 2016 CU8 HF1 here
  • Lync Server 2010 – SfB Client not supported I’m afraid so it suggests Mac 2011 client only.

Client Functionality and Client Comparison

Also worth checking out the Client comparison tables for Skype for Business Server 2015 with the new CU3 update so you know differences between windows and Mac clients.

Screenshots of AuotUpdate , Manual Process and P2P Desktop Sharing

Booted my iMac up and first got asked to update the Microsoft AutoUpdate Tool. I’ve not booted my mac in a while.


Clicked Install







Seem the version available in auto update is the December update. I thought this was applied but lets go.




I also tried Insider Slow got me 16.3.239 which wasn’t the CU3 version.






So perhaps the CU3 update version isn’t available on AutoUpdate just yet.

Manual Install to make sure im on


Find the package in downloads










Nice touch to ask to trash the installer Smile


Checked version using SfB > About.


Manual download is the CU3 version, not sure why AutoUpdate wasn’t updating to this version yet but I’m sure it will soon.

P2P Desktop Sharing look in IM Chat


View from SfB 2016 Client of MAC Client




Download –

More info on CU3 –

Known Issues –

Skype Academy presents Cloud PBX Voicemail with Exchange Server on-premises Summary

I’ve seen this video available for some time on Skype academy and i finally got round to watching it so here’s a summary of the session and some added information. I hope this useful.

Great to see Cloud PBX users can leverage an on premises Exchange deployment for Cloud PBX Voicemail.

Watching the video there are a number of prerequisites and requirements for enabling this and there could be an element of confusion around the use of Azure Voicemail and Exchange UM. Azure VM is still used for voicemail with Exchange server on premises. Also key to note there are some feature missing when using Azure VM Sad smile and also check supportability of existing Exchange Server deployment first and check endpoints compatability.

Link to video –


Speaker Lynnn Roe

Agenda of the session

Previously voicemail options for Cloud PBX relied on having your mailbox in Office 365 (Exchange Online). Voicemail uses Azure Voicemail not Exchange UM and this still seems to be the case if you have Exchange server on premises.

But now Azure Voicemail can leverage your on premises Exchange mailbox with Cloud PBX users. This is great to see this as it allows more flexibility. So now you have mailbox on premises or in Exchange Online Smile


What’s is voicemail for Cloud PBX


KEY POINT – Voicemail is ALWAYS provided by Azure Voicemail it will NOT be provided by Exchange UM.

However Exchange UM policies are required to enable client side features. Voicemail play in Outlook. voicemail displayed in voice tab in SfB client.

Does require a basic exchange dial plan to be configured. UM Mailbox policy to be defined manually with on premises.

Voicemail policy is automatically assigned when online. Manual process on premises.

Some Exchange UM VM feature are not available when using Azure voicemail

  • Play on phone
  • No subscriber Access – not available for Azure Voicemail. Callers cant call into voicemail, listen to calendar or email via PSTN
  • No personal auto attendant – the ability to configure AA is there but it wont work with Azure VM. No real UM functionality

Requirements on end users – No impact on end users

For admin you have to manual configure voicemail on premises! must remember this.



Requirements for mailboxes homed on premises and theres a few of them here


  • Azure AD Sync
  • Exchange DNS points On premises with EWS and autodiscover – Azure VM can learn mailbox is homed on premise
  • Fully configured Exchange Hybrid in place (Mailboxes not migrated)
  • OAuth is configured between Exchange on premises and Office 365 – Enable Azure VM to gain access to users mailboxes on premises
  • Users NOT licenced for Exchange Online – Azure VM
  • Users IS licenced for SfB Online with Cloud PBX
  • Users enabled for UM Dial plan (ON PREMISES Exchange)

The link below expands on the prereqs


KEY POINT – Also published is a supportability matrix which is key to check first.

Note version of Exchange must be Exchange 2013 CU12 which single AD forest.

There are a number of endpoints as well so check this. Lync 2013 client seems be classed as SfB 2013 MSI.




Azure VM elevates mailbox based on licencing to discover mailbox locations.

  • If it has Exchange Online it accesses online mailbox
  • If it doesn’t have a Exchange Online licence it fails and access on premise exchange via EWS and Autodiscover. DNS must be available and accessible externally.

Provides best experience for end users and callers by utilising caching.

DOES require Exchange UM policies

Having Exchange UM policies may cause confusion! i believe it will. Although UM is not used for voicemail processing UM policies are required to be configured. Ouch.

Experience and config requirements for UM policy is the same for on premise and online, difference with online is auto config, on premise is manual by admin


Bit more details on why it works

  • Callers routed initially to Azure voicemail, playback custom voicemail greeting cached
  • Caller experience for person leaving vm is optimised
  • prevents delays for caller leaving vm
  • After vm recorded Azure VM perform lazy back end ops to ensure the next caller has better experience. Lazy ops outside of user experience so no delays or long pauses.
  • Does require and leverage EWs and Autodiscover externally.
  • SMTP failback process, if EWS fails then SMTP will be sent to users inbox.


With diagram as well. Difficult to read fully but you can see how it works.


Calls come in

Azure VM checks for cached custom recordings

If it find cached information this is played to use, if greeting not found a default greeting will be played.

Azure VM will try and authenticate online first, if found send to Exchange online vm if not found route on premises exchange. EWS and Autodiscover used to locate mailbox location. this process could take up to 30 seconds.

After this the information will be cached for the next caller.

SMTP is fall-back if EWS if unavailable.



KEY POINT – SfB Cloud PBX users homed in Office 365 WILL ALWAYS use AZURE VOICEMAIL

KEY POINT – Azure relies on Exchange UM only for client side features to work and be visible. NO UM engine is leveraged for used.

Exchange Hybrid deployment required for Azure VM to locate on premise mailbox


Hope this helps and you found it useful.


Skype Academy presents Tenant Dial Plans (Preview) Summary

So recently Tenant Dial Plans came into Preview in Skype for Business Online and Microsoft published a Skype Academy presents video on Skype Operation frameworks in their technical product training. Below is a summary and the key points i found on watching the video below.

This has for me been a long awaited feature where we can now have custom dial plans as we can do with on premises Skype for Business and Lync Server deployments. Previously SfB Online users have had dial plans assigned automatically by Microsoft which are not customisable and for basic dialling such as calling local, domestic and internationally numbers, no custom normalisation was possible which with users moving from old PBX where this was possible was being seen as a step back and being a potentially roadblock to moving to SfB Online.

What are dial plans ?

A dial plan is a named set of normalization rules that translate dialled telephone numbers by a user into E.164 (Recommended) or can be other number formats but i would always stick to E.164.

Dial Plans themselves are made up of one or more normalization rules which define how phone numbers are translated into an alternate format. Dial Plans can be assigned at given levels for on premises these can be global, site, pool and user. Looks like Online is different with merged dial plans so take note of this.

For example a user will have a dialplan and in that dial plan will be a number of normalization rules that are in affect in the SfB client when a user dials. If a user dials 01782 123456 for UK landline now SfB Online already will normalize this to +441782123456 with the default UK dial plan. Tenant Dial plans for allows SfB Online users to have more flexibility and they can define custom dial plans with custom normalization for extension dialling or local number dialling etc. I feel a very awaited feature !

Link to Video from Skype academy here

Lets go!


Great use of a scenario using Garth who plays a part throughout the video.


Garth works for Contoso

Contoso move from PBX to SfB Online

Garth comes into the Office Monday morning, signs into SfB client and dials 5551234 as he did previously with his PBX desk phone last week.


SfB Client ahs incorrectly normalized this Sad smile

Gareth hits enter and dials and it fails

Garth listens to Diagnostic announcement service which lets him know they have dialled a number incorrectly.


Garth dialled correctly as he was used to with his PBX but the number was normalized incorrectly, a user wouldn’t and shouldn’t have to know about really as its done for them in the background.

Summed up below Garth is SAD and he wished he could dial number like he used to. He’s moved from old legacy PBX phone to SfB and he cant dial like he used which gives a poor user experience from day one Sad smile


SO we need to make Garth happy again Smile here comes Tenant Dial Plans !! Wohoo !


3 Simple things to take away for this session.

Tenant Dial Plans creates support for tenant based custom dial plans in Sfb Online, these rules and dial plans, create custom normalization rules and applicable to specific USER or ENTIRE tenant.

Custom Dial Plans are still in PREVIEW and subject to change as noted below so set expectations on custom dial plans from day one with users if you are using them during the preview. This training is Feb 2017 and current at this time only.

Any Issue please log in Office 365 support portal.


Sign up for Tenant Dial Plans here and requirements to join the preview are below as well.


Tenant Dial Plans and SOF

Break into Plan, Deliver and Operations Phases of SOF.


Plan Phase

What are Tenant Dial Plans??

Based on overwhelming customer feedback, single county specific dial plans are not enough and customers want dial plan customisation that they have or had with on premise deployment for SfB Server in SfB Online. End user experience was impacted when migrated, users felt they had lost out on functionality by moving from PBX to Cloud PBX which isnt good.



  • LIMIT of 25 Normalization rules per dial plan – Key for planning !
  • Applies to Cloud PBX and Hybrid users using CCE and dial out for Cloud PSTN Conferencing !
  • No changes in routing / PSTN usages

Before Tenant Dial Plans

Very basic normalisation rules

Dial plans has always existed but were basic


Now there are two types of dial plans

  • Service – Always existed and has always been applied – CAN NOT be changed
  • Tenant – with two subset types. Default applied to all Office 365 tenants.

Tenant dial plans can be scoped in two different ways:

  • Tenant – Global – applies to all users in tenant
  • Tenant – User – applies to specific subset of users who have been granted this.


How these Dial Plans now work together


Dial plan scope / Hierarchy

Key Point – Hierarchy of Dial Plans works differently to Lync / SfB Server on premises ! Global Site Pool and User, you would apply the lowest level.

If you applied pool level and site to a user then the Pool level would apply, site is ignored completely.


For Tenant Dial plans these are merged together to come up with affective dial plans. Three different categories

1 – No tenant global plans , no user dial plan – only dial plan dialled is service country dial plan

2 – Tenant global , no user level dial plan – Merge Service level and tenant global

3 – Tenant user dial plan – ignore tenant global dial plan and merge tenant user and service country

Found this information as well taken from here

The following is the inheritance model of dial plans in Skype for Business Online.

How dial plans are inherited in Skype for Business Online.

The following are the possible effective dial plans:

Service Country If no tenant scoped dial plan is defined and no tenant user scoped dial plan is assigned to the provisioned user – the user will receive an effective dial plan mapped to the service country associated with their Office 365 Usage Location.

Tenant Global – Service Country If a tenant user dial plan is defined but not assigned to a user – the provisioned user will receive an effective dial plan consisting of a merged tenant dial plan and the service country dial plan associated with their Office 365 Usage Location.

Tenant User – Service Country If a tenant user dial plan is defined and assigned to a user – the provisioned user will receive an effective dial plan consisting of the merged tenant user dial plan and the service country dial plan associated with their Office 365 Usage Location.

Planning Steps


First off Are custom rules required ? Majority of cases this will be required as Service Country as very basic.

  • Can you use tenant global dial plan for all users and keep it simple or do you need user specific ?

No details on creating number plans recommends to look online for other content, ill added some references at the bottom of this post.

Recommendation to maintain consistency on tenant dial plan names !! Key to have a naming standard makes it easier for admins! Same with on premises. Keep it simple !

Also checkout Skype optimizer for all your Dial Plan needs and Tenant Dial plans are coming here to Smile


Have on premise deployed already then check what’s in place and also check if these are actually required or not ? Only use what you need ?

Export from on premises and import to SfB Online

Migration from legacy PBX have a look at old system and add to file to import


Tenant Dial Plans are cmdlet only (Make sure you know how to connect to your Tenant Via PowerShell) Link here

Enable UI in couple of months

Not currently supported with current Cloud PBX Certified IP Phones ! No support was required when qualifying IP Phones as tenant dial plans didn’t exist. This is being looked at in the future.

Working with Tenant Dial Plans


Table displaying scenario and cmdlets to use.

Note – using variables in the cmdlets

7 digits dialled and append +142 infront (Goes back to Garth)

Using Get-csEffectiveTenantDialPlan is a good way to check merged dial plans for users and also testing your rules using –dialledNumber

UseOnPremDialPlan must be set to False if you want Cloud PBX users to use Tenant Dial Plans.

For the PowerShell cmdlets and scripts head over to here for examples from Microsoft you can copy and paste Smile and also details on how to connect via PowerShell to your tenant which is key as there is currently no GUI for tenant dial plans.

In action – Back to Garth




Garth is happy and his normalization is fixed Smile 

Changing Tenant Dial Plan


First we look at deleting a dial plan using remove-cstenantdialplan specify the identity and apply force. Forces removal even if assigned to users. without –force you will have to ungrant it from users first (Recommended way) try not to use –force if possible.


Create input CSV, example above shows example CSV file for importing.

Use CSV in script below


There’s also an example for exporting on premises here which instead of using a CSV it uses XML. Again before exporting and just importing please review if all normalization are actually required ? also remember the 25 normalization rule limit in online as well.


Operate SOF Phase

Some useful troubleshooting information.


What to look for when troubleshooting

Run cmdlet – Get-cseffectivetenantdialplan

Open Client log file with Snooper > Search for LocationProfileDescription


Before – He was assigned Service / Country Dial plan for region

After – Dial Plan has been assigned. Effective dial plan that is combined with Service and Tenant Global. The numbers don’t match as they are merged but the start of the dial plan string is the same.




Key parts for me were

  • Merged dial plans – this is something to remember
  • Limit of 25 normalization rule per dial plan
  • New cmdlets – Using get-cseffectivedialplan is great for troubleshooting
  • No Dial plan UI currently
  • IP Phone doesn’t support tenant dial plans
  • Dial plan naming is as key online as well as on premise


More Details


Create and Manage

Skype Optimizer – Tenant Dial Plans coming soon

Hola Amigos! Skype for Business Cloud PBX with PSTN Calling in Spain GA now

HOLA Amigos ! great news for Spain, Cloud PBX with PSTN Calling in Spain is in GA now.

What is Cloud PBX with PSTN Calling?

Cloud PBX is offered from Skype for Business Online and PSTN Calling is an add service that provides telephony functionality and Microsoft are the PSTN Carrier. Microsoft a telephone number and PSTN calling services and billing. PSTN calling provides users the ability to make and receive phone calls outside of the organization. Cloud PBX with PSTN Calling does not offer the same functionality as an on premises deployment of Skype for Business Server with Enterprise Voice with on premise PSTN providers so be aware of this.

Microsoft are expanding the countries they provide PSTN Calling, France was the one before in early December and now Spain couple of months later has been added so Microsoft have five countries so far and are expanding.

Some highlights on the information I’ve found so far on PSTN Calling for Spain

From Microsoft’s Countries and regions that are supported for Skype for Business Online PSTN Services web page here

Spain is now listed below so in total we now have five countries available


Total Minutes available for Spain

  • 1200 Domestic
  • 1200 Domestic or 600 International minutes (which ever is reached first per month)


Thought id take a peck on on tenant and see what numbers are available.

I can now select Spain and they have a great selection of cities available for numbers which is great.


Overall another great step in expanding Cloud PBX from Microsoft i think and quickly after France went GA as well.

Where next for PSTN Calling from Microsoft ?

Having checked up on i cant see any new countries in preview at the moment but I’m sure it wont be long

Adios Amigos !