Assign licenses to users in Office 365

Activate your Office 365 users by completing the following procedure:

1. Log on to the Office 365 portal page, and then click Users.
2. Select the check box next to the user, or users, that you want to activate, and then click Activate synced users.
3. Under Set user location, select the user’s, or users’, work location.
4. Under Assign licenses, select the licenses that you want to assign to the user, or users, and then click Next.
5. On the Send results in email page, select Send email to send a user name and temporary password by email. Enter email addresses, separated by semicolons (;), and then click Activate. You can enter a maximum of five email addresses.
6. On the Results page, the new user, or users, and a corresponding temporary password are displayed. Click Finish.

Office 365 resource links

Forum
http://community.office365.com/en-us/f/613.aspx

The Lync Transport Reliability IP Probe is located at http://trippsn2.online.lync.com/.

The 32-bit version of the Microsoft Online Services Sign-in Assistant can be downloaded at http://go.microsoft.com/FWLink/p/?Linkid=236299. To download the 64-bit version of the Microsoft Online Services Sign-in Assistant, seehttp://go.microsoft.com/FWLink/p/?Linkid=236300.

The 32-bit version of the Microsoft Online Services Module can be downloaded at http://go.microsoft.com/FWLink/p/?Linkid=236345. To download the 64-bit version of the Microsoft Online Services Module, see http://go.microsoft.com/FWLink/p/?Linkid=236293.

http://msdn.microsoft.com/library/office/dn605892(v=office.15)

Office 365 Development

One of the best overall resources for development against the Office 365 environment is a set of videos by Microsoft available in the Office 365 Developer Training Course. This site does a great job of introducing the features and explaining how they work through development examples and hands-on labs. Outside of this book, this is the next resource to check out.

SharePoint Online Development

Exchange Online Development

Lync Development

Office 365 planning, deployment, and troubleshooting tools

Microsoft and third-party vendors make a number of tools available to enterprise customers. The following list shows the common tools you can use:

• Office 365 Service Descriptions
• Office 365 Deployment Guide
• Microsoft Office 365 Deployment Readiness Toolkit
• Lync Online Transport Reliability Probe (http://trippsn2.online.lync.com/)
• Microsoft Remote Connectivity Analyzer
• IP mapping service to determine data center locations (http://iplocation.net)
• Microsoft Online Services Diagnostics and Logging (MOSDAL) Support Toolkit

There is also an abundance of Office 365 content that is available online. One such resource is the Office 365 admin resource center at http://office.microsoft.com/en-us/support/office-365-administrator-resource-center-FX103995410.aspx. The Office 365 Community site at http://community.office365.com/en-us/forums/default.aspx is another great resource to locate information and request assistance.

Sample code and more
https://github.com/OfficeDev

Directory synchronization and source of authority

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

In a Windows Azure Active Directory (Windows Azure AD) environment, source of authority refers to the location where Active Directory objects, such as users and groups, are mastered (an original source that defines copies of an object) in a cross-premises deployment. Windows Azure AD requires a single source of authority for every object. This reduces the likelihood that directory data could be inadvertently overwritten. By default, Windows Azure AD directory objects are mastered in the cloud, which means they must be edited by using cloud-based tools.

Therefore, when you create objects by using either the Windows PowerShell cmdlet or account portal tools such as the Office 365 portal, you are mastering objects from within the cloud. All subsequent changes to these objects are also made by using the same tools. In this scenario, the source of authority is in the cloud. For more information about the various tools that you can use to create and manage objects in Windows Azure AD, see Administering your Azure AD directory.

Alternatively, when you are running Active Directory synchronization, you are mastering objects from within your on-premises Active Directory. Once Directory Synchronization has been activated, and after the first sync cycle has been completed, the source of authority is transferred from the cloud to the on-premises Active Directory. In this scenario, users, contacts, and groups are created on-premises and then synchronized to the cloud. All subsequent changes to the cloud objects (with the exception of licensing) are mastered from the on-premises Active Directory tools. The corresponding cloud objects are read-only. Administrators cannot edit cloud objects if the source of authority is on-premises.

Directory synchronization roadmap + Deployment

http://technet.microsoft.com/library/hh967642.aspx

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

http://www.techrepublic.com/blog/10-things/10-things-you-should-know-about-deploying-office-365/

1. Synchronization can take a while (can take up to 24 hours)

Troubleshoot errors:

Individual Active Directory Domain Services objects don't sync to Windows Azure AD

http://support.microsoft.com/?kbid=2643629

Troubleshoot directory synchronization

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

IndiIndividual Active Directory Domain Services objects don't sync to Windows Azure ADvidual Active Directory Domain Services objects don't sync to Windows Azure AD