binding contract, contract, secure, agreement, binding, legal, document, contractual, law, business, deal, sign, pen, signature, lawyer, paperwork, obligation, negotiation, finance, commitment, terms, lock, key, bond, committed, guarantee, locked, obligate, watertight contract, promise, word, contract, contract, contract, contract, legal, legal, legal, legal, legal, law, law, law, lawyer, lawyer, commitment, terms, lock, guarantee
Photo by stevepb on Pixabay

Support

Part of Business software installation and licences

Checking licence terms before sharing an account

Check who may use a software licence, whether credentials may be shared and which named-access options fit the work.

This is an editorial pen name used by the publication, not a claim of an independently verified personal identity. Original editorial credit: Desk Support.

Before two workers use one software login, locate the order, product terms and account policy for the exact product, plan and purchase. If unclear, ask the reseller which documents govern. Check who may use the entitlement, whether credentials may be shared, and whether the service offers named users or a collaboration feature.

For Microsoft, a personal Microsoft account is governed by the Microsoft Services Agreement, while work accounts may be subject to the agreement your organisation has with Microsoft instead. Permission for one licensed person to install an app on several devices does not give several people permission to use that person’s account.

Identify what needs sharing

Ask whether staff need the software entitlement, files, an inbox or a task queue. They may need access to the same work while signing in separately. Record the proposed users, their tasks, product edition and seller.

Check the deciding terms

  1. Is access assigned to a person, device, organisation or concurrent-user pool?
  2. If installation on several devices is allowed, who may operate each installation?
  3. May another worker use the credentials, even within the same business?
  4. Does the plan offer named team members, delegation or another approved way to share the work?
  5. Can access be reassigned, and what happens to files associated with the former user?

Microsoft 365 business guidance says to create accounts for people in an organisation and assign a licence to each person. For specified products, it lists device installation allowances.

The Microsoft Services Agreement answers question 3 directly: “You cannot transfer your Microsoft account credentials to another user or entity.” It also makes the account holder responsible for all activity that occurs under the account, so a colleague’s actions on a shared login are the holder’s responsibility.

To see which licence each person holds in Microsoft 365 for business, open the admin centre’s Active users page or Licenses page. Assigning licences needs at least the License or User Administrator role. When a user account is deleted, its licence is immediately available to assign to someone else.

Choose an allowed arrangement

If the proposed shared login is prohibited, arrange eligible accounts or ask the seller for a suitable plan. If staff need the same files or queue, use the service’s permitted sharing or delegation controls. Keep the decision and applicable terms with the software record.

For a shared inbox, Microsoft 365 offers a shared mailbox, and everyone who is a member can see changes to its shared calendar. Shared mailboxes usually don't require a licence, but an Exchange Online Plan 2 licence is needed once more than 50 GB of storage is in use.

The contrast is clear. Two receptionists who each sign in as themselves and open the same shared mailbox follow the terms; two receptionists signing in with one person’s Microsoft account credentials do not.

Seek a written answer from the supplier or seller when the wording remains unclear, before sharing credentials.

A supplier may allow a shared account for a particular use. Where sharing is both allowed and necessary, keep a list of authorised users, use multi-factor authentication where available and change login details when access changes.

More from Support