Office 2013 how many licenses per account

20 to 30 office suites/licenses

From what I've done so far, I've had to create an account to activate the 2013 licenses regardless if OEM or not. 

This new way of activating and licenses is confusing me.

At any rate, thank you Rohn, I much appreciate your prompt responses.

Thank you for you response. I will certainly check into these links. 

I will be using Office 2013 OEM for several clients. I am a field technician and the majority are not interested in Office 365.

I gather that it is not possible to create a generic email account per business/company and activate their licenses through that one generic email account. Is that accurate? For OEM/PKC it allows one license per account?

With 2013 marketing has become murky. Please be exact in your product description.

Office 2013, 1-computer local install is associated with the hardware. The retail license may be transferred to new computers, while the PKC/OEM license cannot.

Office 365 licenses are associated to the email address used to activate them.  365 licenses allow the user to install on up to 5 devices and to control activation / deactivation on specific hardware devices.

It appears that Office 365 Home Premium allows only one 5-computer license per email address. Buying a second license extends the license term, not the count of devices allowed  (this description is based on previous questions, not my personal experience or testing or Official MS confirmation).

Office 365, the various Business licenses, allow you to associate more than one license with a single email address. I have heard the limit is between 10 and 20 licenses, but have not seen official confirmation from MS.    BUT !!! that is not the way MS envisioned using business licenses.  Under the MS concept/plan, each license/product key is associated with a single user. That allows the user to control the install and activation / deactivation of the 5 devices associated with the license.  The business admin has control through a web based portal control center (I have no direct experience with it). It includes some license admin, but I don't know the specifics.

Here are a bunch of links that may provide specific answers to your question

<edit> sorry, some of the hyperlinks were stripped out. I fixed them

Yes the administration of 365 Business licenses is not obvious.  Here are some links that may help clarify the issue for you

License management

A subscription to Office 365 is made up of a number of licenses to a set of services. An administrator assigns a license to each user for each service that user needs access to. For more information about managing licenses, see Assign or remove a license in Office 365 Enterprise,  http://go.microsoft.com/fwlink/p/?LinkID=270069 or  Assign or remove a license in Office 365 Small Business.  http://go.microsoft.com/fwlink/p/?LinkID=270070

Office Deployment Video Business Focus but applies to Home Premium too- Demo install , Side By Side with Older Office

http://officeignitelabs.cloudguides.com/Labs/Office%20Deployment%20and%20Compatibility.htm

Video capture of Office 365 install. First 5 min apply to home users.

CTR allows 2013 365 to run side by side with older versions

App-V 5 and Office 2013

App-V allows an administrator to decouple the application from the operating system. This process allows for the instant deployment of an application, easy application upgrading (without client restarts), and seamless application access control/monitoring.

App-V 5 and Office 2013 – Part 4: Deployment

      http://4sysops.com/archives/app-v-5-and-office-2013-part-4-deployment/

Office Deployment Support Team Blog (index page)

http://blogs.technet.com/b/odsupport/

Lots of interesting and useful “stuff” here.

2013 02 25- Best Windows 8 Deployment Tools

http://www.petri.co.il/best-windows-8-deployment-tools.htm

Brief descriptions of Windows Assessment and Deployment Kit (ADK), MS Deployment Toolkit 2012, System Center Configuration Manager (CM) and Windows Deployment Service (WDS)

Click-to-Run Customization and Deployment Deep Dive Part 1,2,3

http://blogs.technet.com/b/office\_resource\_kit/archive/2013/04/17/the-new-office-garage-series-click-to-run-customization-and-deployment-deep-dive-part-1-with-high-g-aerobatics.aspx

http://blogs.technet.com/b/office\_resource\_kit/archive/2013/04/23/the-new-office-garage-series-click-to-run-customization-and-deployment-deep-dive-part-2-workarounds.aspx

how do I disable certain Office applications from installing. With the MSI you could use the Office Customization Tool to disable components from installing. In Click-to-Run you are installing at a suite or SKU level and to stop people from using them, you would need to first remove shortcuts to the unwanted apps. Then you can use things like AppLocker or similar tools to block executable files from running. If you deploy Office 365 ProPlus with App-V 5 you can prevent applications from installing as part of the Office suite.

We also talked about language management and how you would use language properties in the Office Deployment Tool's configuration XML to download and install Office in different languages.

if you don't have Windows Enterprise required to use AppLocker, Jeremy showed another way to block executables using the AppHelp Hard Block mechanism Windows uses.

http://blogs.technet.com/b/office\_resource\_kit/archive/2013/04/30/the-new-office-garage-series-click-to-run-customization-and-deployment-deep-dive-part-3-integration-and-automation-with-software-distribution-tools.aspx

you can disallow user self-installation in the Office 365 Admin Portal and use software distribution infrastructure exclusively to ensure all Office 365 ProPlus installs happen within your LAN.

"Can we put Office 365 ProPlus and Click-to-Run builds in our Windows images?"

Yes. Whether you preinstall Office in your image then capture it or whether you install Office at build time with a task sequence, both will work. If you are installing and capturing the image, Office has been tested to work fine after running Sysprep.exe. The main thing to remember in that case is you want to install, but not activate Office. So the procedure would be to

install and customize your Windows image,

install Office using the "setup.exe /configure .\configuration.xml" process,

run Sysprep.exe, then

capture with imagex.exe or dism.exe. 

If you are using the Microsoft Deployment Toolkit for imaging, there is another important point to remember

---

Win8 Deployment for Business - 9 part series

---

http://4sysops.com/archives/windows-8-deployment-part-1-the-deployment-share/

Deployment guide for Microsoft Office 2013

http://blogs.msdn.com/b/mssmallbiz/archive/2012/10/22/free-microsoft-ebook-deployment-guide-for-microsoft-office-2013.aspx

Free Download, 147 pg

How does a company install and control licenses - Business

---

Using Click to Run virtualization, the process of getting new users running has substantially changed. Because CTR installations are so fast, you no longer have to pre-install the software for users.

A business IT Admin controls use of corporate Office 365 licenses through the Office 365 Administration Center online.

Overview:

    In the Office 365 Administration Center the designated Office Administrator sets up the new USER ID

    Setup the associated email account(s)

    Setup Office licenses allowed to the userid

    the new User logs in to their new computer

    in Internet Explorer the user goes to the “Office 365 Portal” site to get their allowed Office 365 installation

    using the Click to Run installation process, Office 365 is installed and running on a new computer is a matter of minutes.

The following links will provide you with more detailed information of where to look and what to do. You may require some additional support from an “expert” .

Free MS training for Office 365 Administration Center / Portal

http://office365support.ca/does-microsoft-have-free-training-for-the-new-office-365/

Excellent resource to get you started administering your business Office 365 licenses.

The first video, Exploring the Office 365 Administration Center  http://labs.officeignite.com/Guides/Exploring%20the%20Office%20365%20Administration%20Center.htm  (9:32), describes how to create new userids, and to assign Office licenses to them. It also very quickly breezes by how to install Office.

The second vidow, Office 365 Overview for IT Administrators http://labs.officeignite.com/Guides/Office%20365%20Overview%20for%20IT%20Administrators.htm  (14:00), quickly walks you through setting up new company and users.

On basic setup page, step 3 “Set up User Access” provides links to instructions on how to set up new users.

In Service Settings, Downloads, you can control what Office apps the user can download.

Creating Users for the NEW Office 365

http://office365support.ca/creating-cloud-users-for-the-new-office-365/

This page provides more detailed instructions for setting up the new userids and granting them Office 365 licenses

 Office 365 for enterprises: A tour for administrators

---

http://office.microsoft.com/en-us/videos/office-365-for-enterprises-a-tour-for-administrators-HA102654955.aspx

Office 365 for enterprises brings together the online services your business needs. To see how to set up and manage these services, watch these four short videos.

Where did My MSI go - Deployment Video

http://www.microsoft.com/resources/technet/en-us/office/media/video/video.html?cid=otc&from=mscomoffice&VideoID=670e3969-0509-4d3a-a8a6-ffbe526d3e6f&src=v5:endslate:related^play:related\_0&from=shareembed-syndication

10 minute comparison of MSI and CTR

Touches on corporate provisioning in”User Based License Model Activation”. Users activate/deactivate, but IT still has control to deprovision the license (starting at about minute 8:15).

Then in this video / article :

http://blogs.technet.com/b/office\_resource\_kit/archive/2013/03/20/the-new-office-garage-series-identity-activation-data-access.aspx

They again say the companies can still allow userid activation while maintaining control of the licenses through Active Directory

<snip>

Jeremy: So we showed the installation experience for a domain-joined computer where single sign on is enabled and one that is not domain-joined, but installs via the Office 365 portal. In the direct from portal case when you kick off the installation, you will see a file that looks something like this:

Setup.X86.en-us_O365ProPlusRetail_24*****-45a2-4eeb-b06f-b14****189c8_TX_PR_.exe

In a future episode we'll talk about all of the configurations needed to suppress completely sign-in, first run experiences and user prompts. IT admins have had to deal with these in past releases of Office, but now there are ways to automatically sign users in to Office 365 installs picking up their domain credentials. I also showed the effects of deleting the user account from the Azure AD store and how it put Yoni's Office into Reduced Functionality Mode (RFM) - even if Yoni installs Office on his personal devices using his organization's Office software assets, once Yoni leaves the org the IT department can deprovision his personal installs. That keeps software asset management cleaner and IT is in control.

</snip>

Overview of ID, Authentication and Authorization in Office 2013

<snip  http://blogs.technet.com/b/office\_resource\_kit/archive/2013/04/16/new-poster-and-content-roadmaps-about-office-identity-authentication-authorization-and-security.aspx >

This page has links to 3 posters. The first poster “Identity and Authentication in the Cloud: Office 2013 and Office 365” describes at a high level how to control new user setup in a corporate / small business environment.

</snip>

<snip  http://technet.microsoft.com/en-us/library/jj683102.aspx  >

This page also has a link to the same poster online (http://www.microsoft.com/en-us/download/details.aspx?id=38193 has PDF and Visio versions of the chart). As well, it goes into more detail with information like the following:

… Because Office is a tool that is used by the same individual in two different roles, the new Office offers two identities with which users can log on to Office 2013:

    A Microsoft account, which most people use for personal business

    An organization ID that is assigned by Microsoft, which most people use when doing work for an organization, such as a business, charity, or school.

The credentials that are used to sign in are recognized as either personal or organizational. That sign-in identity becomes the user's “home realm” and determines which documents the user has access to on SharePoint, SkyDrive, or Office 365 Services for a specific session. Each unique sign in identity is saved in a most-recently used list so that it is easy to switch between identities without leaving the Office experience.

….

a personal SkyDrive can be mounted to an organization identity so that personal documents can be accessed at work or school without ever switching identities. Also, when a user authenticates by using an identity, this authentication is valid for all Office applications, not just the application he or she signed in to.

….

Two logon types are supported when users sign in to Office 2013, a Microsoft account or an organization ID that is assigned by Microsoft.

Microsoft account (the user’s individual account). This account, formerly known as Windows Live ID, is the credential that users use to authenticate with the Microsoft network and is frequently used for personal or non-business work, such as volunteer work. To create a Microsoft account, a user provides a user name and password, certain demographic information, and “account proofs,” such as an alternative email address or phone number. For more information about the new Microsoft account, see What is a Microsoft account  http://go.microsoft.com/fwlink/p/?LinkId=268357  ?.

An organization ID that is assigned by Microsoft / Office 365 account ID that is assigned by Microsoft. This account is created for business use. An Office 365 account can be one of three types: a pure Office 365 ID, an Active Directory ID, or an Active Directory Federation Services ID. These are described below:

·         Office 365 ID. This ID is created when an admin sets up an Office 365 domain and takes the form <user>@<org>.onmicrosoft.com, for example:

******@contoso.onmicrosoft.com

·         Organization ID that is assigned by Microsoft that is validated against a user's Active Directory ID. An organization ID that is assigned by Microsoft and validated against Active Directory as follows:

1.      First, a person who has an [on-premise domain]&lt;user> account attempts to access organization resources.

2.      Next, the resource requests authentication from the user.

3.      Then, the user types in their organization user name and password.

4.      Finally, that user name and password are validated against the organization AD database, the user is authenticated, and is given access to the requested resource.

·         An organization ID that is assigned by Microsoft that is validated against a user’s Active Directory Federation Services ID. An organization ID that is assigned by Microsoft and validated against Active Directory Federation Services (ADFS) as follows:

1.      First, one person who has an org.onmicrosoft.com attempts to access partner organization resources.

2.      Then, the resource requests authentication from the user.

3.      Next, the user types in their organization user name and password.

4.      Then, that user name and password are validated against the organization AD database.

5.      Finally, that same user name and password are passed to the partner’s federated AD database, the user is authenticated, and is given access to the requested resource.

For on-premises resources, Office 2013 uses the domain\alias user name for authentication. For federated resources, Office 2013 uses the ******@org.onmicrosoft.com user name for authentication.

</snip>

Office 365 Administration / Office 365 Administration Center / Office 365 Portal

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

This page summarized methods of administering Office 365

User Account Management

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

Sign-in for Small Business subscriptions

Users receive Windows Azure Active Directory cloud credentials—separate from other desktop or corporate credentials—for signing into Office 365 and other Microsoft cloud services.

Sign-in options for Enterprise, Midsize Business, Kiosk, Academic, and Government subscriptions

Office 365 for Enterprise, Midsize Business, Kiosk, Academic, and Government subscriptions has two systems that can be used for user identities:

    Organizational account (cloud identity)   Users receive Windows Azure Active Directory cloud credentials—separate from other desktop or corporate credentials—for signing into Office 365 and other Microsoft cloud services. This is the default identity, and is recommended for small and midsize businesses in order to minimize deployment complexity. Passwords for organizational accounts use the Windows Azure Active Directory password policy.

   Federated account (federated identity)   For all subscriptions other than Office 365 Small Business and Office 365 Small Business Premium, in organizations with on-premises Active Directory that use single sign-on (SSO), users can sign into Office 365 services by using their Active Directory credentials. The corporate Active Directory stores and controls the password policy. For information about SSO, see Single sign-on roadmap.

The type of identity affects the user experience and user account management options, as well as hardware and software requirements and other deployment considerations.

Creating user accounts

Office 365 provides five ways to create user accounts, some of which are not available for Office 365 Small Business and Office 365 Small Business Premium: Add single User, Bulk upload using *.CSV files, Active Directory Synchronization, Azure Active Directory Module for powershell, Exchange Simple Migration

Password management

The policies and procedures for password management depend on the identity system.

Cloud identity password management:

When using cloud identities, passwords are automatically generated when the account is created.

• For cloud identity password strength requirements, see Change your password. http://go.microsoft.com/fwlink/p/?LinkId=268357
• To increase security, users must change their passwords when they first access Office 365 services. As a result, before users can access Office 365 services, they must sign into the Office 365 portal, where they are prompted to change their passwords.
• Admins can set the password expiration policy. For more information for Enterprise and Midsize subscriptions, see Set a user’s password expiration policy. http://go.microsoft.com/fwlink/p/?LinkID=285381   For Small Business, see Change how often passwords expire.  http://go.microsoft.com/fwlink/p/?LinkID=285381

Office 365 for Business FAQ

http://office.microsoft.com/en-us/business/microsoft-office-365-for-business-faq-FX103030232.aspx

2013 02 27- Office 365: Business users' top questions (and answers)

http://www.zdnet.com/microsofts-office-365-business-users-top-questions-and-answers-7000011908/

2013 03 14- Apparently, Microsoft takes this Office 365 (Small Business) support thing seriously

http://www.zdnet.com/apparently-microsoft-takes-this-office-365-support-thing-seriously-7000012613/?s\_cid=e019

<snip> I cannot over-emphasize how important good support is, especially when you can no longer lay your own hands on the server. I also can't over-emphasize how impressed I've become with Microsoft's support for Office 365. </snip>