One of the more popular features requested in Microsoft’s Office 365 video portal is the ability to download the videos for offline use. As it stands today the user experience is that the video streams via your browser or mobile app and the user is not presented with any kind of download option in the UI.
But, we know that the Office 365 video portal is simply built on top of SharePoint so there must be a way to get at the actual video object somehow, right? Good news: you can, as long as you can construct the correct SharePoint URLs.
The root of your O365 Video portal is at this address:
Hitting that URL will simply take you to the O365 Video home page, which isn’t super helpful for saving a video. In order to download a video you’ll want to first identify the channel the video is in and then access this URL to see a SharePoint view of all content within that channel:
Note that the /hub part of the previous URL is not necessary here and if your channel names have a space remember to replace the space with a hyphen, not your typical %20 encoding in the URL. SharePoint replaces the spaces with hyphens when it builds the site URL.
As an example, if my tenant name is confusedamused.onmicrosoft.com and my videos are in a channel called PDX then the URL to see the contents of that channel would be this:
Once you land on that URL you should see thumbnails of all your videos. Hover over any of them and hit the ellipses button to present a download option. Be sure to watch your video at least 5 times to justify the extra effort required to save it for offline access.
Alternatively, if you know the channel and video name you can access it directly with this format:
In the case where your video title has a space in the name you’ll want to use a %20 encoding as usual. And one last note – if a video channel name was ever changed the SharePoint URL will retain the original channel name’s URL path despite the new display name. You can sort out what the original name was via some Fiddler traces if you’re striking out on the URL you’ve created, but that is outside the scope of this post.
When Office 365 Groups first launched last year it was a rather underwhelming first stab at combining a lot of functionality which was arguably already in the Microsoft productivity stack, and in pretty much every case, way more refined than Groups.
We’ve seen incremental changes to the Groups feature over the past few months and the messaging seems to point that all roads from Exchange, SharePoint, and Lync/Skype for Business eventually lead to Groups. There is still a long list of control knobs and discovery refinements needed before this is something an enterprise can fully adopt, but there are some use cases which make Groups appealing today.
One of the main motivators for using a social tool like Yammer instead of a traditional distribution list is that it captured the historical content. So the person who starts the day after someone posts a critical message to the entire team actually has access to the previous conversations and content. Groups solves that problem quite well, even if it’s difficult for an administrator to manage that content. But let’s face it – Yammer’s admin features are sorely lacking as well, so if you’re willing to give up tagging and notifications then Groups is a viable alternative.
I wanted to share a few quirks I’ve noticed if you’re headed down this path:
Logo and Image Sizing
The photo you set for the Group logo should be 240×240 pixels. I can’t find this documented anywhere, but that seems to be the size of the example or stock image you’ll see when the group is created. But, OWA and OneDrive for Business show different quality levels for reasons I can’t explain. The first image here is what I see in OWA and the second is the logo in OneDrive for Business when I access the files section, which looks obviously blurry.
If you try to manage the Group within the Azure AD Access Panel you may find that you’re then unable to manage some options back in the OWA interface. For example, I created this Group within OWA as a public group anyone could join. I modified the permissions in Azure AD to require approval. Now – even as the Group owner – I’m unable to revert that setting in OWA and see the Privacy section is grayed out.
Default SMTP Address
Groups default to using your tenant ID as the primary SMTP address. Really smart folks on my team like Keif Machado and Joe Stocker have already beaten this one to death, but let’s just say it’s inconsistent with what anyone would expect when creating a new object. Remember to flip it to an appropriate domain after creation.
It’s getting social, and we’re starting to see even more overlap with Yammer functionality. I can “Like” a message anyone posts and they will receive a notification that I did so. But, that pop-up notification is only visible in OWA, so the Outlook stalwarts will surely suffer from a lack of ego-boosting alerts.
There seems to be some semblance of the presence concept, and perhaps we’re seeing the starting to see these groups becoming a persistent chat room in Skype for Business. When you view the contact card for a group you’ll see the presence indicator on the left side just like any other contact. I’ve seen it change from Available to Away with not much background on why, but it’s obvious that some aspect of the group has presence abilities.
Something that is coming up more and more on Lync projects is the concept of integrating with newer video and collaboration services like Acano or Pexip. It’s very important to understand that the deployment guides from these services request you create a static route from your Lync Front End pools to their MCUs. This in itself is not a red flag, especially since this is how some of the Polycom DMA or Cisco VCS integration has worked in the past.
However, this does pose a problem for organizations looking to leverage split-domain with Lync Online, or more commonly, Exchange Online being leveraged for voicemail while Lync Enterprise Voice remains on-premises. The issue here is that using your primary SIP domain as the Match URI in the static route to these video services prevents the signaling from getting to your federation Edge servers (at least, as of the latest Lync 2013 CUs.) The static routing configuration seems to kick in before the call is ever routed to the Edge, so the concept of the CsHostingProviders and the shared address space is never respected.
Let’s walk through an example:
My primary SIP domain in Lync is @confusedamused.com.
I migrate my mailboxes to O365 and enable the Exchange Online shared address space. My voicemail is hosted in O365.
I want to host large meetings in O365 so I also enable the Lync Online shared address space for hybrid. I have some users homed to O365.
Everything works fine at this point.
I now want to integrate with Acano or Pexip. I create a static route for @confusedamused.com which goes from my Lync FEs to their bridges.
This breaks both Exchange Online voicemail routing and communication to Lync Online users.
The real solution here is to use a different SIP domain for your video routing, which as undesirable as this may be to end users, has arguably been a best practice for a long time. Create the static route matching @video.confusedamused.com, @acano.confusedamused.com, or @pexip.confusedamused.com. Take your pick, or create your own variation. It just needs to be different from the SIP domain you actually assign to Lync users.
This is important to grasp if you’re using Lync Online or Exchange Online today and looking to add video, but probably even more critical from a roadmap standpoint. Exchange Online Unified Messaging is a fairly common use-case today, and Lync Online hybrid is becoming more and more popular. Planning ahead for these scenarios and any potential video integration will help you avoid these issues.