Archive for the ‘Office365’ Category

SQL Query to Find Active Resources for Licensing

Monday, December 14th, 2015

SQL Query to Find Active Resources for Licensing

V: 1.2, MD: 01/24/2017

Following SQL query will show the list of users that are active, that connected to Project Web App (PWA) since specified date (Oct 1st, 2015 or the date you specify) and should be counted towards the licensing.

* Contact Softvative for accurate licensing assessment of your SharePoint or Project Server PPM farms. We have done Software Asset Management (SAM) projects for customers where we worked with the software vendors to save the licensing costs. We have skills in Microsoft MAP, System Center and other custom tools for the SAM.

Click here to download the SQL query file.

Replace the syntax with your Project Server database name.

 

 

SharePoint Server 2016 Announcement and My Wish List

Tuesday, February 3rd, 2015

Version: 1.1,

Updated: 2/3/2015

Microsoft has been pushing for Office 365 and SharePoint Online for last few recent years. They recently announced that next version of SharePoint Server will be released in 2016.

SharePoint Server 2016 will offer customers enhanced, flexible deployment options, improved reliability and new IT agility, enabled for massive scale. SharePoint Server 2016 is expected to provide rich hybrid capabilities with Office 365 version.

SharePoint Server 2016 – My Wish List of Feature

I wish for many new and improved features in next version of SharePoint Server in 2016. Following are some of the top wishes based on my experience with customers.

  1. More enriched workflows
  2. Document Scanning Feature
  3. Making Project Server as completely independent application that can be used without the need of full SharePoint Enterprise. (in recent years we have seen Office Web Apps as an application that requires separate server for deployment now)
  4. Making better across the farm security reporting (without the need to 3rd party tools)
  5. Better Forms solution that has better cross platforms compatibility (InfoPath replacement)
  6. Making an On-Prem version of Yammer as a service application or separate app that can be tightly integrated with SharePoint
  7. Making Video Encoding features available for more enriched video publishing within on-prem
  8. Making Delve available in On-Prem as well

I’ll be adding more items later. Read the following Office blog post with recent announcement details.

References:

Visit www.softvative.com for professional services.

Yammer Feed Integration with SharePoint Online Common Issues

Monday, December 15th, 2014

Version: 1.3

Scenario:

I had an external Yammer Network with few groups underneath it. I had a SharePoint Online (Office 365) site collections with sub-sites. I created three pages under the main site and leveraged three different option (one on each page) to integrate the Yammer Feed with the SharePoint Online site.

a. Yammer App for SharePoint by Microsoft – http://o15.officeredir.microsoft.com/r/rlidYammerappO15?clid=1033

b. Yammer Feed Embed – By Blue Rooster – https://bluerooster.uservoice.com/forums/239290-yammer-feed-embed

c. Yammer Embed Code – Go into a Yammer Group. On bottom right look under Access Options section

Yammer Feed Integrated with SharePoint Online (in Office 365)
Yammer Feed Integrated with SharePoint Online (in Office 365)

Issue Details

Everything was working until an unknown bump caused the feed to break. I started getting the following Yammer Login message no matter even if I click on login icon and go through the Yammer login page to login using ADFS login.

Yammer Feed Integration keeps displaying Yammer login on SharePoint online page even after login
Yammer Feed Integration keeps displaying Yammer login on SharePoint online page even after login

Error 2
In one instance on a page, I got the following frame error.

content cannot be displayed in a frame
   
To help protect the security of information you enter into this website, the publisher of this content does not allow it to be displayed in a frame.

What you can try:
Open this content in a new window

Yammer Feed Integration with SharePoint Online can't display contents in frame error
Yammer Feed Integration with SharePoint Online can’t display contents in frame error

Findings:

I found the Yammer Support on Twitter and asked them about the issue. They were quick to point me to the Yammer Status page that showed there was disruption on that day.

The issue was only happening when using Internet Explorer. Chrome was able to display the feed.

I switched to Yammer group Enterprise Social (Yammer) Help. I started a conversation on this Yammer issue there.

Resolution:

There are few pieces of the Yammer-SharePoint marriage puzzle.

  1. Add the Yammer, SharePoint Online and MicrosoftOnline login sites to the IE Trusted Sites list. That was done using AD GPO
  2. In IE settings, for the trusted sites check the box ‘Enable Protected Mode (requires restarting Internet Explorer)’
  3. Users should have access to the SharePoint site pages and the Yammer Network / Group feed that is embedded
  4. SharePoint page URL format can make or break Yammer Feed on the page

1. Adding Sites URL to Internet Explorer Trusted Sites for the Yammer Feed to work in SharePoint Online:

I found a Microsoft article that talks about adding Yammer feed to a SharePoint page. See the section ‘Having trouble with the app’ in that article. I then worked with the AD / security team to make the change in the GPO to add the Yammer, SharePoint and MicrosoftOnline links to the IE trusted zone.

We added these links to the Active Directory Group Policy for computers.

https://login.microsoftonline.com
https://*.sharepoint.com
https://*.yammer.com
https://*.assets-yammer.com

Using Group Policy Management Console (thanks to RSAT for Win7), I was able to view the changes. Once you have the RSAT installed and configured, you can use the server tools from your desktop. Open ‘Group Policy Management’ from Start > Administrative Tools or type gpmc.msc in Start > run and enter.

In the Group Policy find the GPO that applies the Internet Explorer trusted site settings to computers.

Active Directory - Group Policy Management Console
Active Directory – Group Policy Management Console

Expand the Organization Unit (OU) from left that contains the computers and click on the Group Policy. Click on Settings tab and then expand all settings by clicking Show All. Look for Internet Explorer related settings.

Active Directory - Group Policy Management Console - Settings
Active Directory – Group Policy Management Console – Settings

I found the Yammer, SharePoint and MS online urls were added there.

Active Directory - Group Policy Management Console - IE Trusted Zone Settings
Active Directory – Group Policy Management Console – IE Trusted Zone Settings

You can optionally save the GPO settings as report. Right click on the right side settings area and choose Save Report. Save the report in .htm format.

Active Directory - Group Policy Management Console - GPO Settings - Save Report
Active Directory – Group Policy Management Console – GPO Settings – Save Report

I was still getting the issue due to reason that the AD GPO policy changes were not applied to my PC. I ran the gppdate from the command line and closed IE browser windows.
Online.

Gpupdate /force /target:computer

Client side Group Policy Force Updates using gpupdate
Client side Group Policy Force Updates using gpupdate

I then logged on to SharePoint Online and Yammer again.Guess what, now the ‘feeds were feeding’ the SharePoint

Yammer Feed Integrated on a SharePoint Online page
Yammer Feed Integrated on a SharePoint Online page

2. In IE settings, for the trusted sites check the box ‘turn on protected mode in trusted zone’

In few cases, especially with IE 11, the users have to make sure the ‘Enable Protected Mode (requires restarting Internet Explorer)’ is checked for trusted sites.

a. In Internet Explorer, Go to Tools menu > Internet Options
b. Go to Security tab
c.  Click on Trusted Sites icon to highlight it and then check the box ‘Enable Protected Mode (requires restarting Internet Explorer)

Enable Protected Mode (requires restarting Internet Explorer)' in Internet Explorer for Yammer SharePoint
Enable Protected Mode (requires restarting Internet Explorer)’ in Internet Explorer for Yammer SharePoint

3. Users should have access to the SharePoint site pages and the Yammer Network / Group feed that is embedded
User visiting a SharePoint page with the Yammer network / group feed embedded on the page, should have access to Yammer network / group. Else user will get content can’t be displayed message in the app part (web part) area on that page.

This content cannot be displayed in a frame
    
To help protect the security of information you enter into this website, the publisher of this content does not allow it to be displayed in a frame.
    
What you can try:

Open this content in a new window  

Yammer Feed can not be displayed in the Frame Error on a SharePoint Online (Office 365) page
Yammer Feed can not be displayed in the Frame Error on a SharePoint Online (Office 365) page

If you click on the link ‘Open this content in a new window‘, you will see the yammer page for that network displaying ‘Join Network’ link. that indicates that the user doesn’t have permissions or is not part of the Yammer network that was embedded on that SharePoint Page.

Yammer - Join Yammer Network Page - SharePoint Integration
Yammer – Join Yammer Network Page – SharePoint Integration

Users that will be part of the network should be able to see the feed on the SharePoint online Page.

4. SharePoint page URL format can make or break Yammer Feed on the page

I’ve noticed another issue where the URL address format of the SharePoint page can make or break the Yammer feed integrated on a SharePoint page.

For a same site, notice the difference in URL:

Yammer Feed Worked:
https://company.sharepoint.com/sites/SiteCollection/subsite/SitePages/Home.aspx

Yammer Feed Failed:
https://company.sharepoint.com/sites/SiteCollection/subsite/_layouts/15/start.aspx#/SitePages/Home.aspx

In case of the second link, Yammer feed displays the same message ‘This content cannot be displayed in a frame’ as listed above in one of the screenshot. Investigating this issue further.

References:

  1. Yammer-App-for-SharePoint-Add-a-Yammer-feed-to-a-SharePoint-page
  2. Yammer Embed
  3. Office 365 URLs and IP address ranges
  4. Ragner Heil – Yammer App for SharePoint & Office 365 : Tips & Trick
  5. Setting Up Apps and Integrating Yammer into SharePoint 2013
  6. SharePoint Server 2013 known issues


Keywords:

  • Yammer Feed Integration with SharePoint Online
  • Yammer Feed Integration with SharePoint Online Issues
  • Yammer Feed Integration Common Issues
  • Yammer Feed Integration Issues
  • SharePoint Online with Yammer Common Issues
  • Yammer Feed Integration with SharePoint Online fixes
  • Yammer Feed Integration with SharePoint Online resolutions
  • Yammer Feed with SharePoint Online Fixes
  • How to integrate Yammer feed with SharePoint
  • How to integrate Yammer feed with SharePoint Online
  • How to integrate Yammer feed and SharePoint
  • Yammer group Feed Integration with SharePoint Online
  • Yammer network Feed Integration with SharePoint Online
Visit www.softvative.com for professional consulting services.

Softvative Microsoft Office365 Applications Brainstorming Plan

Sunday, November 16th, 2014

Office 365 Applications Brainstorming Plan

Version: 1.1

Microsoft Office 365 has lots of applications based on the plan you choose. To make it easy to plan and understand, Softvative created a brainstorming plan. the initial version if focused on external user interactions with corporate users.

Soon that plan will be offered as a full version download for registered users. The full version will be a MS Visio based version covering Visio plan, clickable links to important articles, comments on key areas and expanded plan with more details.

Review the current version of the Office 365 brainstorming plan that includes key Microsoft Online apps including:

  • Office 365
  • SharePoint Online
  • Project Online
  • Yammer
  • OneDrive for Business
  • Skype for Business (Lync)
  • Exchange Online
  • CRM Online
  • Power BI

SharePoint Document Conversion Services

Wednesday, October 29th, 2014

SharePoint Document Conversion Services

Version: 1.0

Applies to:

  • SharePoint 2010
  • SharePoint 2013
  • SharePoint Office 365

Overview of Document Conversion Services

SharePoint has Document Conversion Service that allows to convert files like Microsoft Word .docx into SharePoint webpages.

Office Web Apps (web version of Office) that works in SharePoint and allows users to view Office files even if they don’t have MS Office installed on their PC. In the absence of Office Web Apps (OWA), SharePoint Document Conversion Service will be handy to view the MS Office files.

Document Conversion services are not enabled by default. There are two services for Document Conversion.

1. Document Conversion Launcher Service
2. Document Conversion Load Balancer Service

Configuring Document Conversion Services

To enable the document conversion, you have to first configure its Load Balancer Service and then the Launcher service.

a. Configure Document Conversion Load Balancer service on SharePoint Application Server (Central Admin > Services on Server: ApplicationServer)

b. Configure Document Conversion Launcher Service on SharePoint Application Server (Central Admin > Services on Server: ApplicationServer)

c. Configure the Document Conversions (Central Admin > General Application Settings > Configure Document Conversions)

Issues in Configuring Document Conversion Services

Some times you get into issue during initial configuration of Document Conversion service or even later during operations where these services fail to start.

Error Starting Document Conversion Services

You go to SharePoint Central Administration site > System Settings > Manage Servers in this Farm > Click on an application server name (not SharePoint Web Front End). That will bring you to the Services on Server: ServerName page. In one of my scenario, I tried to start the Document Conversion Load Balancer service and got Error Starting status. I tried different ways but couldn’t start the service.

SharePoint Document Conversion Launcher Service - Error Starting status
SharePoint Document Conversion Launcher Service – Error Starting status

I went into Event Viewer logs first on the SharePoint application server and found following errors.

Event Viewer Error 1

Log Name:      Application
Source:        Microsoft-SharePoint Products-SharePoint Foundation
Date:          10/28/2014 3:12:46 PM
Event ID:      7034
Task Category: Topology
Level:         Critical
Keywords:      
User:          softvativeSPFarmServiceAccount
Computer:      SharePointAppSrv.softvative.com
Description:
An attempt to start/stop instance  of service Document Conversions Load Balancer Service on server 

SharePointAppSrv did not succeed.  Re-run the action via UI or command line on the specified server. 

Additional information is below.

Operation is not valid due to the current state of the object.
Event Xml:
<Event xmlns=”http://schemas.microsoft.com/win/2004/08/events/event”>
  <System>
    <Provider Name=”Microsoft-SharePoint Products-SharePoint Foundation” Guid=”{6FB7E0CD-52E7-47DD-

997A-241563931FC2}” />
    <EventID>7034</EventID>
    <Version>14</Version>
    <Level>1</Level>
    <Task>13</Task>
    <Opcode>0</Opcode>
    <Keywords>0x4000000000000000</Keywords>
    <TimeCreated SystemTime=”2014-10-28T20:12:46.879677800Z” />
    <EventRecordID>858925</EventRecordID>
    <Correlation ActivityID=”{4A13B121-2470-406B-ADCB-2A97903E8D0D}” />
    <Execution ProcessID=”19412″ ThreadID=”788″ />
    <Channel>Application</Channel>
    <Computer>SharePointAppSrv.softvative.com</Computer>
    <Security UserID=”S-1-5-21-1627688274-1190192956-3999157559-1223″ />
  </System>
  <EventData>
    <Data Name=”string0″>
    </Data>
    <Data Name=”string1″>Document Conversions Load Balancer Service</Data>
    <Data Name=”string2″>SharePointAppSrv</Data>
    <Data Name=”string3″>Operation is not valid due to the current state of the object.</Data>
  </EventData>
</Event>

SharePoint Document Conversion Error - Event ID 7034
SharePoint Document Conversion Error – Event ID 7034

Event Viewer Error 2

Log Name:      Application
Source:        Microsoft-SharePoint Products-Document Management Server
Date:          10/28/2014 3:12:11 PM
Event ID:      7953
Task Category: Document Conversions
Level:         Critical
Keywords:      
User:          softvativeSPFarmServiceAccount
Computer:      SharePointAppSrv.softvative.com
Description:
The Office HTML Load Balancing Service experienced a problem.

Error:  Not launching Document Conversions Laod Balancer because registry key acknowledging service 

running on app server (‘AcknowledgedRunningOnAppServer’) is not set.
Event Xml:
<Event xmlns=”http://schemas.microsoft.com/win/2004/08/events/event”>
  <System>
    <Provider Name=”Microsoft-SharePoint Products-Document Management Server” Guid=”{F78D66EC-09A9-

42A2-AC7A-5EE2062DE7E4}” />
    <EventID>7953</EventID>
    <Version>14</Version>
    <Level>1</Level>
    <Task>8</Task>
    <Opcode>0</Opcode>
    <Keywords>0x4000000000000000</Keywords>
    <TimeCreated SystemTime=”2014-10-28T20:12:11.098100000Z” />
    <EventRecordID>858923</EventRecordID>
    <Correlation />
    <Execution ProcessID=”10552″ ThreadID=”16556″ />
    <Channel>Application</Channel>
    <Computer>SharePointAppSrv.softvative.com</Computer>
    <Security UserID=”S-1-5-21-1627688274-1190192956-3999157559-1223″ />
  </System>
  <EventData>
    <Data Name=”string0″>Not launching Document Conversions Laod Balancer because registry key 

acknowledging service running on app server (‘AcknowledgedRunningOnAppServer’) is not set.</Data>
  </EventData>
</Event>

SharePoint Document Conversion Error - Event ID 7953
SharePoint Document Conversion Error – Event ID 7953

Event Viewer Error 3

Log Name:      Application
Source:        Microsoft-SharePoint Products-Document Management Server
Date:          10/28/2014 3:12:11 PM
Event ID:      7960
Task Category: Document Conversions
Level:         Critical
Keywords:      
User:          softvativeSPFarmServiceAccount
Computer:      SharePointAppSrv.softvative.com
Description:
The Office HTML Load Balancing Service could not be started.

Error:  Not launching Document Conversions Laod Balancer because registry key acknowledging service 

running on app server (‘AcknowledgedRunningOnAppServer’) is not set.
Event Xml:
<Event xmlns=”http://schemas.microsoft.com/win/2004/08/events/event”>
  <System>
    <Provider Name=”Microsoft-SharePoint Products-Document Management Server” Guid=”{F78D66EC-09A9-

42A2-AC7A-5EE2062DE7E4}” />
    <EventID>7960</EventID>
    <Version>14</Version>
    <Level>1</Level>
    <Task>8</Task>
    <Opcode>0</Opcode>
    <Keywords>0x4000000000000000</Keywords>
    <TimeCreated SystemTime=”2014-10-28T20:12:11.095099700Z” />
    <EventRecordID>858922</EventRecordID>
    <Correlation />
    <Execution ProcessID=”10552″ ThreadID=”16556″ />
    <Channel>Application</Channel>
    <Computer>SharePointAppSrv.softvative.com</Computer>
    <Security UserID=”S-1-5-21-1627688274-1190192956-3999157559-1223″ />
  </System>
  <EventData>
    <Data Name=”string0″>Not launching Document Conversions Laod Balancer because registry key 

acknowledging service running on app server (‘AcknowledgedRunningOnAppServer’) is not set.</Data>
  </EventData>
</Event>

SharePoint Document Conversion Error - Event ID 7960
SharePoint Document Conversion Error – Event ID 7960

Services in Console

In one of my scenario, I went into Windows Services console to review the Document Conversion services. Both the services were not running. Don’t try to start the services from Windows Service console.

SharePoint Document Conversion Services in Windows Services Console
SharePoint Document Conversion Services in Windows Services Console

Root Cause

It turns out there are registry keys that were needed to acknowledge that you configured the services to run on the application server.

Registry Location:
HKEY_LOCAL_MACHINESOFTWAREMicrosoftOffice ServerversionLauncherSettings
HKEY_LOCAL_MACHINESOFTWAREMicrosoftOffice ServerversionLoadBalancerSettings

Replace version based on SharePoint version:
SharePoint 2007 -> 12.0
SharePoint 2010 -> 14.0
SharePoint 2013 -> 15.0

You need to add the new key AcknowledgedRunningOnAppServer of type dword and set it to 1. That will let you start the Document Conversion services from Central Admin site.

SharePoint Document Conversion Launcher Settings - AcknowledgedRunningOnAppServer Key
SharePoint Document Conversion Launcher Settings – AcknowledgedRunningOnAppServer Key

SharePoint Document Conversion Load Balancer Settings - AcknowledgedRunningOnAppServer Key
SharePoint Document Conversion Load Balancer Settings – AcknowledgedRunningOnAppServer Key

My Registry Script

I created the AcknowledgedRunningOnAppServer registry entries as a registry file for easy import on new servers in future.

Download the Document Conversion Registry Fix files (.reg or .zip)

Download the .reg file or .zip file and extract the zip file contents to a folder. Locate the DocumentConversion_RegSettingKB2910363.reg file and double click on it. Click Yes to the message box.

Add the Document Conversion Registry Keys to SharePoint Application Server Registry
Add the Document Conversion Registry Keys to SharePoint Application Server Registry

Click OK to the successful message box.

Added Document Conversion Registry Keys to SharePoint Application Server Registry
Added Document Conversion Registry Keys to SharePoint Application Server Registry

After adding the registry entries, try to start the Document Conversion Load Balancer Service from the Central Admin site > Services on Server page. Click on Start under action column to start the Load Balancer service.

SharePoint Document Conversion Load Balancer Service Started
SharePoint Document Conversion Load Balancer Service Started

Now click on Start under action column for the Document Conversion Launcher Service. That will brig the Launcher Service Settings page. Select the same server from Load Balancer dropdown field and click OK.

SharePoint Document Conversion Launcher Service Settings
SharePoint Document Conversion Launcher Service Settings

You should now see the two Document Conversion services with the status of started.

SharePoint Document Conversion Services with Started Status
SharePoint Document Conversion Services with Started Status

Let take a peak at the Windows Service console for these services.

SharePoint Document Conversion Services -Started in Services Console
SharePoint Document Conversion Services -Started in Services Console

Configure Document Conversions

Once the Document Conversion services are running, its time to configure it. You go to Central Admin site > General Application Settings > Configure Document Conversions to configure the conversions.

SharePoint - Configure Document Conversions link
SharePoint – Configure Document Conversions link

On Configure Document Conversions page, you select the web application, enable document conversion, select a load balancer, schedule conversion and set converter settings. Click Apply. Once you are done with changes, then click OK.

SharePoint - Configure Document Conversions Settings
SharePoint – Configure Document Conversions Settings

Under Converter Settings, click on one of the link for the installed converters to review and adjust settings.

SharePoint Document Converter - From Word Document to Web Page Converter Settings
SharePoint Document Converter – From Word Document to Web Page Converter Settings

I’ll demonstrate more including some the limitations on Document Conversion in next version of the this article. Hop over to this page later to review the updated version.

References

  1. Configure Document Conversions Load Balancer and Launcher Services
  2. Document conversion load balancer unavailable
  3. Configure the Document Conversions Load Balancer Service
  4. Manage document conversions
  5. Some document-conversion services in SharePoint Server are not secure when they run in a particular environment

Sharepoint On Premise Office365 and Hybrid – Pros, Cons and Comparison

Sunday, August 10th, 2014

SharePoint On Premise Office365 and Hybrid –

Pros, Cons and Comparison

On SharePoint fronts there has been so much going on with different editions and versions. I created this presentation to do a quick overview, Pros / Cons and comparison of three flavors of SharePoint:

  1. SharePoint On-Premise
  2. Office 365 SharePoint
  3. Hybrid (combination of 1 and 2)

View my presentation and email me your feedback.

Sharepoint 365 Initial Talking Points

Thursday, July 31st, 2014

Sharepoint 365 Initial Talking Points

V: 1.0

With Office 365, Microsoft introduced the SharePoint Online aka SharePoint 365 version. Recently I’ve been going through lots of information on SharePoint 365 version. I came up with few initial talking points to give a good start with the Office 365 SharePoint.

There are many things to consider when thinking of migration:

  • User experience
  • Identity management
  • Data Security
  • Feature set
  • Integration with internal systems
  • Even how you budget your dollars for next year

Suggestions:

  1. Role Based Access Control
  2. Two Factor Authentication
  3. Combine Search results from On-Premise and Office 365 SharePoint
  4. Multiple Authentication Options

a. MS Online ID        Example: faisal.masood@softvative.onmicrosoft.com
b. MS assigned Org ID AD Login Example: ADDomainfmasood
c. MS assigned Org ID ADFS Login Example: faisal.masood@softvative.onmicrosoft.com accessing partner organization’s resources

AD Integration Options:

a. Directory Sync OnlyDirSync. Runs every 3 hr and uses SQLExpress for less than 50K AD objects. For more objects, use full SQL. No Full SSO or 2FA
b. Directory Sync and SSO Suited for large orgs. Needs HA for ADFS. 2FA possible. Identities managed on-premises.

AD Integration Requirements:

a. Requires your AD forest at 2003 level
b. Use x64 bit DirSync tool. 32bit deprecated
c. For ADFS setup Win 2008 or 2012 server. Can be virtual
d. Dirsync tool can be setup with one-way or two-way sync. Two-way sync required for hybrid scenarios and can’t be switched back to one-way.
e. Use Office 365 deployment readiness tool to check your on-premises AD
f. Have the AD DC, ADFS, DirSync on seperate servers

Reference Links:

1. Steps to configure Single Sign On for Office 365
http://blogs.msdn.com/b/sharepoint__cloud/archive/2011/12/07/steps-to-configure-single-sign-in-for-office-365.aspx

2. Using multiple federated domains in Office 365 with Okta

https://community.okta.com/docs/DOC-1266

3. Microsoft Office 365 Deployment Readiness Tool

https://technet.microsoft.com/en-us/library/hh852475.aspx

4. ADFS with Office 365



5. Description of Update Rollup 1 for Active Directory Federation Services (AD FS) 2.0

http://support.microsoft.com/kb/2607496

6. Support for Multiple Top Level Domains

http://community.office365.com/en-us/w/sso/support-for-multiple-top-level-domains.aspx

7. 10 things you should know about Office 365 before signing up

http://www.bfcnetworks.com/blogs/alexpearce/10-things-you-should-know-about-office-365-before-signing-up/

8. Use third-party identity providers to implement single sign-on

http://technet.microsoft.com/en-us/library/jj679342.aspx

9. How To Install ADFS 2012 R2 For Office 365

http://blogs.technet.com/b/rmilne/archive/2014/04/28/how-to-install-adfs-2012-r2-for-office-365.aspx

10. Remote Authentication in SharePoint Online Using Claims-Based Authentication

http://msdn.microsoft.com/en-us/library/hh147177.aspx

11. Ignite Office 365



12 SharePoint Online Service Description

https://technet.microsoft.com/en-us/library/jj819267.aspx

13. Multi-Factor Authentication for Office 365

http://blogs.office.com/2014/02/10/multi-factor-authentication-for-office-365/