In December 2017, the new Microsoft Graph reporting APIs were announced:
https://techcommunity.microsoft.com/t5/Office-365-Blog/Announcing-the-General-Availability-of-Microsoft-Graph-reporting/ba-p/137838, also in this announcement was the deprecation of the Office 365 Reporting Web Service:
- ConnectionbyClientType
- ConnectionbyClientTypeDetail
- CsActiveUser
- CsAVConferenceTime
- CsP2PAVTime
- CsConference
- CsP2PSession
- GroupActivity
- MailboxActivity
- GroupActivity
- MailboxUsage
- MailboxUsageDetail
- StaleMailbox
- StaleMailboxDetail
While writing the Manage-AzureAppRegistration script (
http://realtimeuc.com/2017/12/manage-azureappregistration/), I found some interesting problems setting Oauth2Permissions. My original code would lookup the Service Principal for an API to assist with determining the ID for the specific role I was adding. The problem quickly became apparent that not all Tenants had the same list of Microsoft Service Principals and even if they did, the Display Name could be different.
Let’s just assume that a Skype for Business Cloud Connector Edition (CCE) has been deployed successfully, the steps to configure an online hybrid Mediation Server (
Configure online hybrid Mediation Server Settings) was completed and at one time PSTN calls could be escalated to an Audio Conference. Fast forward a few months and users report PSTN call escalation fails every time.
When accessing some of the Microsoft Graph API endpoints, you can get away with leveraging the well known Client ID reserved for PowerShell: “1950a258-227b-4e31-a9cf-717495945fc2”. Of course luck would have it, the few items I wanted to access (Microsoft Graph Reporting API and Office 365 Management Activity API) are not granted to the PowerShell Client ID.
Over the last year a handful of clients have requested assistance around configuring the Line URI for Meeting Rooms in Skype for Business Online when using Cloud Connector Edition (CCE) and Microsoft Phone System. Running the Set-CsMeetingRoom cmdlet with the -lineuri parameter, will greet you with a nice “Unable to set “LineURI”. This parameter is restricted with Remote Tenant PowerShell” error.
A journey for your amusement:
December 2012: I submitted my first Lync Server 2013 (RTM) bug. The problem was when an organization enabled for federation with a conferencing policy allowing to invite anonymous users and a meeting organizer had an External Access Policy disabling federated user access. The result would be an external participant could join this meeting if using the web app, but would fail to join if using the desktop client.
Last week Microsoft Teams Guest Access became generally available (
https://blogs.office.com/en-us/2017/09/11/expand-your-collaboration-with-guest-access-in-microsoft-teams). This feature is not meant to replace Federation (
Please Vote!), but I’m using this as a stop gap until Federation is available.
The New Voicemail User Settings Features for Skype for Business Online Preview has finished and stopped on-boarding customers at the end of August 2017. In testing and confirmation from multiple clients not part of this preview program, the feature seems to have gone live in the public over the last few days.
Today I’m shedding light on the SIP 404 response status code while working with Skype for Business Online’s CloudPBX and Cloud Connector Edition (CCE). The “404 Not Found” error is masked in the Skype for Business Client as “We couldn’t reach +1XXXXXXXXXX” during an outbound PSTN call.
On July 31, 2017 Microsoft announced the Teams Outlook add-in to schedule meetings:
https://techcommunity.microsoft.com/t5/Microsoft-Teams-Blog/Now-available-Outlook-add-in-to-schedule-meetings-in-Microsoft/ba-p/71157
Excited to give this a run through its paces, I noticed Outlook was missing the Teams button under New Items and when creating a new Meeting.
