Can this agreement be signed electronically?

Yes. Electronic signatures are legally enforceable in the United States under the ESIGN Act (15 U.S.C. §7001) and UETA where adopted. Ensure intent, consent, attribution, and reliable record retention to meet the four-part ESIGN/UETA test.

Who must sign on behalf of a company?

An authorized representative with board or officer-level signing authority should sign. The signature block should include printed name, title, and date; internal delegations or corporate resolutions may be required to prove authority.

What if actual seat usage exceeds the agreement?

Overuse typically triggers audit remedy clauses: notify the licensor, reconcile counts, and pay remediation fees. Maintain regular seat audits to avoid surprise liability and back-billing.

Is notarization or witnesses required?

Not generally required for commercial software licenses. Notarization and witnesses are rare for these contracts unless state-specific formalities or corporate execution requirements apply.

How should amended terms be documented?

Use written amendments signed by both parties referencing the original agreement. Record effective dates and retain a consolidated executed copy to avoid competing versions in audits or disputes.

How do you revoke or terminate a license?

Follow termination clauses in the agreement, including notice, cure periods, and post-termination obligations. For suspensions related to breach, document remediation steps and communications to support legal positions.

Electronic Signature
Templates
Miscellaneous
Microsoft Office License Agreement

Microsoft Office License Agreement

This template is fully customizable. Edit the text, fill out the fields, and send it for signature. Give it a try!

MICROSOFT OFFICE LICENSE AGREEMENT

This Microsoft Office License Agreement (the Agreement) is made and entered into as of Effective Date: by and between Licensor Name: and Licensee Name: .

RECITALS

WHEREAS, Licensor lawfully possesses rights to distribute and license copies of the Microsoft Office software product identified as Product Name: (the Software); and

WHEREAS, Licensee desires to obtain and Licensor desires to grant a license to use the Software under the terms and conditions set forth in this Agreement; and

WHEREAS, the parties intend to set forth their mutual rights and obligations with respect to delivery, payment, support, confidentiality and liability.

SCOPE OF WORK

Description of Licensed Software and Services

LICENSE GRANT; RESTRICTIONS

1. Grant. Subject to the terms and conditions of this Agreement, Licensor grants to Licensee a non-exclusive, non-transferable, limited license to install and use the Software for License Quantity: authorized users/devices for the Term defined below.

2. Restrictions. Licensee shall not: (a) sublicense, rent, lease, assign, distribute or transfer the Software except as expressly permitted herein; (b) reverse engineer, decompile or disassemble the Software except to the extent permitted by applicable law; or (c) remove or alter proprietary notices.

License type (select all that apply): Perpetual Subscription Volume

PAYMENT TERMS

License Fee Payment Schedule and Terms Late Payment

If Licensee fails to pay any amount when due, Licensee shall pay interest on the overdue amount at the rate of percent per month, or the maximum permitted by law, whichever is lower, plus all costs of collection, including reasonable attorneys' fees.

TERM AND TERMINATION

Term Commencement Date: Term End Date:

Either party may terminate this Agreement for convenience upon written notice to the other party at least days prior to the effective termination date. Licensor may terminate this Agreement immediately if Licensee materially breaches any provision and fails to cure within thirty (30) days after written notice.

CONFIDENTIALITY

Each party shall maintain in confidence all Confidential Information of the other party and shall not disclose such information to any third party except to employees, contractors or advisors with a need to know and who are bound by confidentiality obligations at least as protective as those contained herein. Confidential Information includes non-public business and technical information, trade secrets, pricing, and any information marked confidential.

Exceptions to Confidential Information (if any)

MAINTENANCE, SUPPORT AND UPDATES

Licensor will provide updates and maintenance as described in the Scope of Work. Unless otherwise agreed in writing, updates that are critical security fixes shall be provided at no additional charge; feature updates may be subject to additional fees as set forth in the Payment Terms.

WARRANTY; DISCLAIMER

Licensor warrants that, at the time of delivery, the Software will materially conform to the specifications set forth in the Scope of Work. EXCEPT FOR THE FOREGOING LIMITED WARRANTY, THE SOFTWARE IS PROVIDED "AS IS" AND LICENSOR DISCLAIMS ALL OTHER WARRANTIES, EXPRESS OR IMPLIED, INCLUDING WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, AND NON-INFRINGEMENT.

INDEMNIFICATION; LIMITATION OF LIABILITY

Licensee shall indemnify and hold harmless Licensor from claims arising out of Licensee's misuse of the Software. Licensor shall indemnify Licensee against third-party claims alleging that the Software, as delivered, infringes a valid U.S. patent, copyright, or trade secret, provided Licensor is given prompt notice and sole control of the defense and settlement.

Except for liability arising from willful misconduct or a party's indemnification obligations, each party's aggregate liability under this Agreement shall not exceed the amounts actually paid by Licensee to Licensor under this Agreement in the twelve (12) months preceding the claim.

Liability Cap (optional)

ASSIGNMENT; SEVERABILITY

Neither party may assign this Agreement without the prior written consent of the other party, except that Licensor may assign to an affiliate or successor in interest. If any provision is found invalid or unenforceable, the remaining provisions shall remain in full force and effect.

NOTICES

All notices under this Agreement shall be in writing and delivered to the addresses set forth below or to such other address as a party may designate by notice in accordance with this section.

Licensor Notice Address Licensee Notice Address

GOVERNING LAW; ENTIRE AGREEMENT

This Agreement shall be governed by and construed in accordance with the laws of the State of without regard to conflict of law principles. The parties submit to the exclusive jurisdiction of the courts located in that State for disputes arising under this Agreement.

This Agreement, including any Schedules and the Scope of Work, constitutes the entire agreement between the parties with respect to the subject matter hereof and supersedes all prior and contemporaneous agreements, representations and understandings, whether oral or written.

EXECUTION

The parties have executed this Agreement by their duly authorized representatives as set forth below.

Licensor (Printed Name):

By:

Date:

Licensee (Printed Name):

By:

Date:

What a Microsoft Office License Agreement Covers

A Microsoft Office License Agreement is a contract that defines the right to use Microsoft Office software, including licensed products, permitted users, number of seats, term, updates, and support. It sets out license scope (per-user, per-device, or enterprise), restrictions on copying or redistribution, maintenance and upgrade policies, and billing or renewal terms. The agreement also typically addresses audit rights, indemnification, limitation of liability, and governing law. Organizations use it to establish legal permissions and operational controls for deploying Office across devices and users.

Why a Clear License Agreement Matters

A well-drafted Microsoft Office License Agreement reduces legal and compliance risk, clarifies permitted use, prevents unexpected audit exposure, and sets renewal and support expectations.

Core Elements to Include in a Professional Agreement

A complete agreement organizes rights and obligations into concise sections so both licensor and licensee understand permitted uses, fees, support, and enforcement.

Grant of License

Describe the exact license type, scope, and whether rights are exclusive, transferable, or limited to specific devices or users.

Term & Renewal

Specify start and end dates, automatic renewal terms, notice periods for nonrenewal, and conditions for termination or suspension.

Payment Terms

State fees, billing frequency, late-payment remedies, and whether pricing is per user, per device, subscription, or perpetual.

Updates & Support

Outline entitlement to updates, security patches, support windows, service levels, and how critical fixes are delivered.

Audit & Compliance

Define audit rights, required documentation for seat counts, remediation steps for overuse, and associated fees or remedies.

Liability & Indemnity

Allocate responsibility for third-party claims, limit damages where appropriate, and include any indemnity obligations.

Step-by-Step: How to Prepare and Execute the Agreement

Follow these steps to assemble, approve, and sign a Microsoft Office License Agreement in a compliant, auditable way.

01

Gather details: Collect legal names, SKU numbers, seat counts, and billing information.
02

Draft terms: Insert license grant, term, fees, audit process, and support provisions.
03

Internal approvals: Obtain procurement, legal, and IT sign-off before executing the contract.
04

Execute: Sign using permitted method; retain executed copy with audit trail.

How Electronic Execution Typically Flows

E-signature workflows simplify execution and maintain a complete audit record from sender to final storage.

Upload document: Add final agreement PDF to your eSignature platform.
Place fields: Insert signature, date, and initial fields where required.
Authenticate signer: Choose email, SMS code, or stronger ID verification.
Capture audit trail: Store timestamps, IP addresses, and action history with the signed file.

Recommended eSignature Workflow Settings for Licenses

Configure workflows to ensure identity, traceability, and preservation of the final executed agreement.

Field	Configuration
Signature Method	Use ESIGN-compliant electronic signatures with recorded audit trail.
Authentication	Email plus optional SMS or KBA for higher-risk signers.
Template Reuse	Save standard license templates to reduce drafting variance.
Audit Trail Retention	Retain signed copies and logs according to your records retention policy.

Platforms and Integrations for Managing Licenses

Choose platforms that integrate with your procurement and identity systems to reduce manual reconciliation.

Microsoft 365: Exchange and user provisioning integration
CRM / ERP: Salesforce or NetSuite contract lifecycle linkage
Cloud Storage: Box, Google Drive, or SharePoint archival

Integrations help automate seat tracking, renewal reminders, and central storage for audits and compliance reviews.

Security and Compliance Features to Verify

Transport Encryption: TLS 1.2 / 1.3

At-Rest Encryption: AES-256

Audit Trail: Timestamped actions and IP logs

Certifications: SOC 2 Type II

Healthcare Compliance: HIPAA (BAA available)

Regulatory Support: 21 CFR Part 11 capability

Key Risks and Potential Consequences

License Audit: Monetary remediation

Overuse Fees: Back-billing for excess seats

Termination: Suspension of product access

Indemnity Claims: Third-party liability exposure

Compliance Breach: Regulatory penalties

Data Loss: Operational disruption

Common Preparation Mistakes to Avoid

Using an informal or trade name instead of the registered legal entity causes enforcement and payment issues during audits.
Failing to specify license type or SKU leads to ambiguity over permitted installations and feature entitlements.
Not tracking seat counts and active users increases the likelihood of surprise audit remediation fees and reconciliation disputes.
Omitting renewal notice periods or automatic renewal terms causes unexpected renewals or missed termination windows.

Comparison: signNow and Common eSignature Vendors

Pricing and feature lines are presented to help compare fundamental capabilities for signing and managing license agreements across vendors.

	signNow	DocuSign	Adobe Sign	PandaDoc	HelloSign
Starting Price	$8/user/mo	$15/user/mo	$14/user/mo	$19/user/mo	$15/user/mo
Free Trial	Yes, 7-day trial	Varies by plan	Varies by plan	Varies by plan	Varies by plan
Bulk Send	Yes	Yes	Yes	Yes	Yes
Audit Trail	Yes	Yes	Yes	Yes	Yes
HIPAA Compliant	Yes	Yes	Yes	No	No
Envelope Cap	No cap	100 envelopes/user/year	Varies	Varies	Varies

Who Typically Prepares and Signs These Agreements

Several internal roles collaborate to evaluate, approve, and execute Microsoft Office License Agreements.

IT procurement managers who quantify seat counts and deployment scope for technical compliance.
Legal counsel who negotiate terms, indemnities, and governing law provisions with vendors.
Finance or procurement officers who approve budgets, payment terms, and renewal commitments.

Coordination among IT, legal, and finance reduces ambiguity and ensures the organization meets licensing and audit obligations.

Real-World Use Cases

These short examples show how different organizations structure license agreements to match operational needs.

Mid-market IT deployment

A regional firm standardized on per-user subscriptions

enabled automated seat provisioning
The template reduced onboarding time and clarified renewal obligations for IT and finance.

Healthcare system contract

A hospital added a BAA and data-hosting commitments

required signed addenda for PHI processing
The executed agreement aligned vendor obligations with HIPAA retention and breach-notification requirements.

Frequently Asked Questions

Answers to common questions about execution, e-signature validity, and practical considerations for Microsoft Office License Agreements.

Need help? Contact support

Can this agreement be signed electronically?
Yes. Electronic signatures are legally enforceable in the United States under the ESIGN Act (15 U.S.C. §7001) and UETA where adopted. Ensure intent, consent, attribution, and reliable record retention to meet the four-part ESIGN/UETA test.
Who must sign on behalf of a company?
An authorized representative with board or officer-level signing authority should sign. The signature block should include printed name, title, and date; internal delegations or corporate resolutions may be required to prove authority.
What if actual seat usage exceeds the agreement?
Overuse typically triggers audit remedy clauses: notify the licensor, reconcile counts, and pay remediation fees. Maintain regular seat audits to avoid surprise liability and back-billing.
Is notarization or witnesses required?
Not generally required for commercial software licenses. Notarization and witnesses are rare for these contracts unless state-specific formalities or corporate execution requirements apply.
How should amended terms be documented?
Use written amendments signed by both parties referencing the original agreement. Record effective dates and retain a consolidated executed copy to avoid competing versions in audits or disputes.
How do you revoke or terminate a license?
Follow termination clauses in the agreement, including notice, cure periods, and post-termination obligations. For suspensions related to breach, document remediation steps and communications to support legal positions.

be ready to get more

Join over 28 million airSlate SignNow users

Sign Now