For those using SharePoint Online, you may have noticed that it does not provide the same home realm discovery that Exchange Online does, with Home Realm discovery meaning the services knows what domain/upn is being used and leveraging that authentication type for the user (Managed/Online versus Federated/ADFS). SharePoint Online support now supports Sign-In Acceleration, which allows SPO to understand whether a browsing user is a Federated user and send to https://login.microsoftonline.com, with a directive that instructs login.microsoftonline.com to then forward the authentication request on to their ADFS deployed endpoint (i.e. https://sts.contoso.com).
Note – To enable this for your Office 365 tenant, please log a support case for this request and they can fulfill your request!
Once auto-acceleration is enabled, the SPO authentication process works as follows:
- The user navigates to https://contoso.sharepoint.com in their web browser.
- SharePoint receives the request and detects that auto-acceleration is enabled for this tenant by leveraging the domain name in the domain.sharepoint.com URL being used to access SPO.
- The user is then sent to login.microsoftonline.com with extra information in the URL (a whr tag). This tag indicates to AAD that it is safe to accelerate the user directly to the ADFS endpoint, login.contoso.com.
- Once there, the user may enter their credentials and sign-in. In the case of domain-joined machines, the user will be signed in immediately based on browser settings for SSO.
This effectively allows SPO to provide home realm discovery and SSO for users, like Exchange Online does today and will make your SPO users much more happy, reducing the authentication prompts and requests for UPNs/Passwords.
For those Office 365 Admins who are responsible for Outlook Web Access (OWA) and the new Document Collaboration feature, allowing Office 365 Web Apps to render the attached document and provide document editing and collaboration. While this is a great new addition, as Exchange previously would not allow or provide the ability to edit these attached documents, as the Exchange Information Store did not have that capability. So now instead of having to save the attached document to a local PC, fileshare, SharePoint Online, etc and then edit the document, the attached documents can now have full editing capabilities, which is FANTASTIC!
So your next question might be “How do I manage this? While I like this capability, my users may not be ready, I need to get everyone trained on this before rolling this out. How do I manage this?”
…special thanks to Bala K. for the following information
Steps to Manage Enablement/Disablement of OWA Document Editing
- Connect to Exchange Online via PowerShell
- $LiveCred = Get-Credential
- $Session = New-PSSession -ConfigurationName Microsoft.Exchange -ConnectionUri https://ps.outlook.com/powershell/ -Credential $LiveCred -Authentication Basic -AllowRedirection
- Import-PSSession $Session
- Once connected, you will manage this OWA Document Editing Capability by managing the OWAMailboxPolicy attribute for the Exchange Online tenant level for all users:
- Set-OwaMailboxPolicy -Identity OwaMailboxPolicy-Default -WacViewingOnPublicComputersEnabled $False -WacViewingOnPrivateComputersEnabled $False
Note – When using this new feature notice that the attached document has three elipsys (dots) which give users the ability to select if they want to download, otherwise clicking the document will open the attached document into Editing View:
For SharePoint Online of Office 365 Global Administrators who need to control what links your SharePoint Online users see when browsing throughout SharePoint, this article is for you.
The SharePoint Online Admin Center now has a new option to control which links are provided for your end users. To manage these options, use the following steps:
- Browse to your SharePoint Online Admin Center, similar to:
- Browse to Service Settings
- Note the very first option displayed, allowing you to manage which links are provided for your users, regarding OneDrive for Business, Yammer/Newsfeed or SharePoint “Sites”:
For those administrators who have multiple workloads/services that require migration into the cloud or Office 365, this article is for you. Special thanks to those who have helped in pulling this list together, to hopefully help those who have the challenge of migrating and moving into the Office 365 environment.
Microsoft Migration Guide for Exchange and Lync workloads here:
Third Party Migration Tools & Services:
For those SharePoint Online Admins who are responsible for licensing and site cleanup, this post is for you. A great write-up on this can be found here, however for brevity’s sake, the important information is listed below:
Note – While the above references SharePoint 2010, using the MySites Moniker for people’s personal SharePoint sites, SharePoint Online 2013 references SkyDrive Pro as the new name for this feature. While the above reference is to SharePoint 2010, the SkyDrive Pro/MySite “clean-up” process is still used in SharePoint 2013.
The My Site Cleanup Job is responsible for deleting user profiles and My Sites of those users. This includes the following activities:
- Remove user profiles that are queued for deletion.
- If those users have a My Site, assign the user’s manager as the SPSite.SecondaryContact. Email the manager letting them know that the user’s My Site will be deleted in 14 days.
- 11 days after the first notification, email the manager again letting them know that the My Site will be deleted in 3 days.
- After a total of 14 days, delete the MySite.