Posts
Assigning a phone number to a user in Skype for Business Online requires you to first assign an Emergency Location. The Emergency Location is used for saftety and liability purposes in case someone were to dial an emergency number (ex: 911 in the USA). The location is sent to the PSAP (Public Safety Access Point, i.e. police, firefighter, ambulance, etc) so they can show up to the correct address and provide help. Take a look at the picture below from my tenant. Notice under 'Dallas,' my address is listed. Underneath 'Dallas' is my actual apartment number (all addresses blacked out for privacy). Skype for Business Online allows for a parent/child relationship with Emergency Locations. For example, if there are multiple floors in a building, you could create a parent location of 'Minneapolis Office' with each floor of the building as a child item (Floor 1, Floor 2, etc). While this flexibility is great, it presents problems when assigning Emergency ...
Well, this is odd. I was helping a customer in an Office 365 Hybrid Deployment. They decided to go with S4B on prem and Exchange in the cloud. The customer tested scheduling a S4B Meeting and noticed the following: ( Dial-In Conferencing Numbers are blacked out, but trust me, they're the same. ;) ) Why is this a thing? I wasn't for certain, however, my best guess was this was either being caused by the O365 Pro Plus Client or Exchange. Time to troubleshoot! I checked S4B Technet Forums and found a post from another user regarding this same issue. I followed the advice in the post above and had the customer schedule a meeting through OWA rather than through their client. Low and behold, scheduling the meeting through OWA listed the dial-in conferencing number once. Alright, now I'm getting somewhere, but what's going on with the client? The customer was running the most recent O365 First Release Deferred Channel Version (v 1701 as of June 2017)...
