Office 365 Cloud PBX Alert: Cloud PBX Update Changes How Delegate Caller ID Works

dont - Copy

UPDATE: Fixed (at least for us) on 1/17/2017

NOTE: With the new Office 365 Cloud PBX “stream of updates” model we are trying to figure out how this blog can best provide value to the community as a Office Server & Services (Skype for Business) MVP. We think special bulletins affecting Cloud PBX changes may be one of them so we are starting a class of blog article called Office365 Alerts. These updates will be very time sensitive since the cloud is in constant change. This is the first such blog.


- As of today Office 365 is rolling out an update to Cloud PBX (Skype for Business Online) that changes how Calling Out as a Delegate (Calling on Behalf of another user) works.

In the past when you call out as a delegate the Caller ID would be that of the the user you were calling out as. For example: If an admin is calling out as a boss, the remote party would see the caller ID of the Boss. The “new” way is that the caller ID is that of the admin.

Our consulting team got notified by some customers that it was no longer working as it had in the past. We tested it on our own tenant and it worked as we were used to it working. The next day it changed to the new way. We checked with Office 365 support and were told that an update is being rolled out as we speak, which is apparently changing the behavior.

This will especially impact:

  • Attendant console operators acting as admins (boss/admin scenario)
  • IP phone users acting in boss/admin scenario
  • Those who might be using a work around to accommodate fact that Office 365 Cloud PBX doesn’t currently have the ability to have a single outgoing DID for a company or group

At the moment we are not sure if this was an intentional design change or accidental.

No comments:

Post a Comment

Note: Only a member of this blog may post a comment.