Can this be electronically signed?

Yes. Electronic signatures are generally enforceable under the federal ESIGN Act (15 U.S.C. §7001) and UETA where adopted; confirm that the transaction is not an excluded document type such as wills or certain court orders.

Is notarization required?

Not ordinarily for a services extension unless state law or a specific party requires notarization; if notarization is required, consider Remote Online Notarization procedures where allowed.

Do I need a BAA for healthcare data?

Yes. If the extension covers protected health information, include a Business Associate Agreement and confirm HIPAA safeguards and breach notification timelines.

How do we update the extension after signing?

Amendments require a written modification signed by authorized representatives of both parties; document versioning and execution history should be retained for audit purposes.

How should executed extensions be stored?

Store signed copies in the contract repository with immutable audit trails and backups; retain supporting security evidence per retention policies and regulatory requirements.

What if signer name or title is wrong?

A name or capacity mismatch may undermine enforceability; correct errors via a signed amendment or re-execution to ensure authority and attribution are clear.

Electronic Signature
Templates
Miscellaneous
Cloud Services Enablement Extension

Cloud Services Enablement Extension

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

CLOUD SERVICES ENABLEMENT EXTENSION

Effective Date:

Parties

Client Name: Client Address:

Client Primary Contact:

Client Contact Email:

Service Provider Name: Provider Address:

Provider Primary Contact:

Provider Contact Email:

Recitals

WHEREAS, the parties entered into a Cloud Services Agreement titled dated (the "Agreement");

WHEREAS, the parties desire to extend and amend certain enablement services and associated deliverables described in the Agreement on the terms set forth in this Extension; and

NOW, THEREFORE, in consideration of the mutual covenants contained herein and other good and valuable consideration, the receipt and sufficiency of which are acknowledged, the parties agree as follows:

1. Scope of Work

Provider shall perform enablement services to configure, integrate, and operationalize the cloud services described below. Work will be performed in accordance with the deliverables, timelines, and acceptance criteria set forth herein and in any applicable statement of work incorporated by reference.

Describe Enablement Services and Deliverables:

2. Payment Terms

Client shall pay Provider the fees set forth below for the extended enablement services. Fees are exclusive of taxes unless otherwise required by law.

Total Fee for Extension (USD): Payment Schedule (select applicable option):

One-time payment upon invoice Milestone payments per statement of work Monthly recurring enablement fee

Invoices and Payment Terms: Late Payment Fee:

3. Term and Termination

This Extension shall commence on and shall continue until unless earlier terminated in accordance with this Section.

Either party may terminate this Extension for convenience upon days' prior written notice to the other party. Either party may terminate immediately for material breach if the breaching party fails to cure the breach within thirty (30) days after receipt of written notice specifying the breach.

Termination of this Extension shall not relieve Client of its obligation to pay for services performed and expenses incurred prior to the effective date of termination, nor shall it affect any provision which expressly or by implication survives termination.

4. Confidentiality

Each party acknowledges that during the term it may receive Confidential Information of the other party. "Confidential Information" means non-public information, whether in oral, written, electronic or other form, disclosed by one party to the other that is marked confidential or that reasonably should be understood to be confidential given the nature of the information and the circumstances of disclosure, including pricing, technical designs, system architecture, and customer data.

The receiving party shall: (a) use Confidential Information solely to perform its obligations under the Agreement and this Extension; (b) restrict disclosure to employees, contractors, and agents with a need to know and who are bound by confidentiality obligations at least as protective as those herein; and (c) exercise at least the same degree of care to protect the disclosing party's Confidential Information as it uses to protect its own confidential information, but in no event less than reasonable care.

Confidential Information shall not include information that is or becomes publicly known through no wrongful act of the receiving party, or which is independently developed without use of the disclosing party's Confidential Information, or that is rightfully obtained from a third party without restriction. Upon termination of this Extension, each party shall promptly return or destroy Confidential Information as directed by the disclosing party, except to the extent retention is required by law or reasonable record retention policies.

5. Data Security and Access

Provider shall implement and maintain administrative, physical, and technical safeguards appropriate to the nature of the Client Data to protect against unauthorized access, disclosure, alteration, or destruction. Specific security obligations, access controls, and incident response responsibilities shall be as set forth in the original Agreement and any applicable addenda, and remain in full force and effect for the duration of this Extension.

6. Governing Law; Dispute Resolution

This Extension shall be governed by and construed in accordance with the laws of , without regard to conflict of law principles. The parties agree to negotiate in good faith to resolve any disputes; if unresolved, disputes shall be resolved in accordance with the dispute resolution provisions contained in the Agreement.

7. Entire Agreement; Amendment

Except as expressly modified by this Extension, all terms and conditions of the Agreement remain unchanged and in full force and effect. This Extension, together with the Agreement and any incorporated statements of work, constitutes the entire agreement between the parties with respect to the subject matter hereof and supersedes all prior and contemporaneous agreements and understandings, whether written or oral. Any amendment to this Extension must be in writing and signed by authorized representatives of both parties.

8. Miscellaneous

No waiver of any breach or default hereunder shall be effective unless in writing and signed by the waiving party. If any provision of this Extension is held invalid or unenforceable, the remaining provisions shall remain in full force and effect. Neither party may assign its rights or obligations under this Extension without the prior written consent of the other, except to an affiliate or in connection with a merger, acquisition or sale of substantially all assets.

Notice Address for Client: Notice Address for Provider:

Client Name:

By:

Date:

Provider Name:

By:

Date:

What the Cloud Services Enablement Extension Covers

A Cloud Services Enablement Extension is a contractual addendum that defines how a vendor will deliver, secure, and support cloud-hosted services under an existing agreement. It typically clarifies scope of services, data handling and residency, security controls, subprocessors, service levels, incident response, and transition obligations. The extension aligns technical and operational commitments with legal responsibilities so both parties understand rights, risk allocation, and practical steps for onboarding, audits, and termination while keeping the master agreement intact.

Why organizations add a Cloud Services Enablement Extension

The extension creates a focused, auditable record of cloud-specific obligations—security controls, data flows, uptime commitments, and compliance responsibilities—so stakeholders can manage risk and demonstrate adherence to regulatory or contractual requirements.

Teams that commonly complete this extension

Stakeholders from procurement, IT security, legal, and vendor management typically collaborate to prepare and approve the extension.

Procurement and vendor managers who need clear service and pricing terms for cloud deployments.
Information security and compliance teams who must confirm controls and supporting attestations.
Legal counsel who negotiate liability, indemnity, and data protection clauses.

The final signatories often include an authorized contracting officer for the buyer and an executive or authorized representative for the cloud provider.

Core sections to include for a professional extension

A complete Cloud Services Enablement Extension organizes obligations into discrete, actionable sections so reviewers can find security, compliance, and operational commitments quickly.

Scope

Precise description of services, environment boundaries, and any excluded components to avoid operational ambiguity.

Data Handling

Classification of covered data, permitted uses, residency requirements, and data lifecycle rules for collection, storage, and deletion.

Security Controls

Required technical and organizational controls (encryption, access controls, logging) and reference to evidence such as SOC 2 or ISO 27001 reports.

Subprocessors

List of subprocessors or process for notice and approval, plus obligations for subprocessors to meet the same controls.

Incident Response

Notification timelines, escalation path, forensics cooperation, and regulatory disclosure responsibilities after a security event.

Termination & Transition

Data return or secure deletion procedures, export assistance, and any post-termination access or migration support.

Security and compliance items to verify

Encryption: TLS 1.2/1.3 in transit; AES-256 at rest

Certifications: SOC 2 Type II; ISO 27001

Regulatory: ESIGN and UETA compliance

Healthcare: HIPAA with BAA available

Audit Trail: Tamper-evident logs and timestamps

Accessibility: WCAG 2.0 Level AA where applicable

Step-by-step process to prepare and sign the extension

Follow these sequential steps to complete review, approval, and execution with minimal rework.

01

Draft: Populate fields and attach supporting security exhibits.
02

Internal Review: Legal and security validate clauses and evidence.
03

Vendor Review: Exchange redlines and reach negotiated text.
04

Execution: Authorized signers sign and record the fully executed extension.

How to configure a digital signing workflow for the extension

Configure a repeatable workflow so each extension follows the same review and signing path.

Field \| Configuration	Field Name \| Required/Optional \| Format
Authentication	Email plus SMS OTP for external signers
Field Types	Signature, date, initials, checkbox, text block
Conditional Logic	Enable conditional clauses based on selected services
Routing Order	Sequential: Legal → Security → Procurement → Executive

Where to send or file the completed extension

Use consistent submission targets and repositories so the extension is discoverable and auditable.

Contract Repository: Store the executed extension with the master contract.
Vendor Records: Ensure vendor retains a signed copy and provides access to buyer.
Procurement System: Attach the extension to the purchase order or SOW record.
Security Evidence Vault: Retain supporting compliance reports and attestations.

Technical formats and integrations for electronic completion

Confirm accepted file formats and integrations before starting the e-signature workflow.

File Formats: PDF, DOCX, or HTML are widely supported
Integrations: Salesforce, NetSuite, Microsoft 365, Google Workspace
API & Export: PDF/A export and audit log support

Choosing compatible formats and integrations reduces conversion errors and keeps metadata and audit trails intact during signing and storage.

Typical timelines and processing expectations

Establish clear internal deadlines so reviews, approvals, and execution do not delay project onboarding.

Internal Review Target:

3–7 business days for legal and security review

Vendor Response Time:

5–10 business days for redline and countersign

Execution Window:

30 days from final agreement to fully executed signature

Operational Onboarding:

Begin provisioning within agreed SLA after execution

Audit Availability:

Provide evidence on request within 10 business days

Common mistakes to avoid when preparing the extension

Leaving scope vague and relying on verbal assurances, which leads to disputes about deliverables and support obligations.
Failing to identify subprocessors or to require subprocessors to meet equivalent security commitments, increasing third-party risk.
Using nonstandard data classification language that conflicts with internal policies or regulatory definitions, causing compliance gaps.
Neglecting retention and deletion procedures, which can create regulatory exposure and complicate incident response.

Key risks and potential consequences

Enforceability: Ambiguous terms can render obligations unenforceable

Regulatory Fines: HIPAA violations may trigger penalties and corrective actions

Data Exposure: Inadequate controls increase breach risk and liability

Operational Delay: Unclear SLAs can delay provisioning and revenue recognition

Audit Findings: Missing evidence may lead to failed compliance audits

Contract Disputes: Poor change control creates costly remediation

eSignature solution pricing and feature comparison

Basic vendor pricing and feature availability can affect cost estimates for executing and managing extensions; confirm plan details with each provider.

	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	7-day free trial	Varies by plan	Varies by plan	Varies by plan	Varies by plan
Bulk Send	Yes (Business Premium)	Yes	Yes	Yes	No
Audit Trail	Yes	Yes	Yes	Yes	Yes
HIPAA Compliant	Yes (BAA available)	Yes	Yes	No	No
Envelope Cap	No envelope cap	100 envelopes/user/year	Varies by plan	Varies by plan	Varies by plan

Frequently asked questions about the Cloud Services Enablement Extension

Answers to common legal, technical, and process questions to reduce delays during review and execution.

Need help? Contact support

Can this be electronically signed?
Yes. Electronic signatures are generally enforceable under the federal ESIGN Act (15 U.S.C. §7001) and UETA where adopted; confirm that the transaction is not an excluded document type such as wills or certain court orders.
Is notarization required?
Not ordinarily for a services extension unless state law or a specific party requires notarization; if notarization is required, consider Remote Online Notarization procedures where allowed.
Do I need a BAA for healthcare data?
Yes. If the extension covers protected health information, include a Business Associate Agreement and confirm HIPAA safeguards and breach notification timelines.
How do we update the extension after signing?
Amendments require a written modification signed by authorized representatives of both parties; document versioning and execution history should be retained for audit purposes.
How should executed extensions be stored?
Store signed copies in the contract repository with immutable audit trails and backups; retain supporting security evidence per retention policies and regulatory requirements.
What if signer name or title is wrong?
A name or capacity mismatch may undermine enforceability; correct errors via a signed amendment or re-execution to ensure authority and attribution are clear.

be ready to get more

Join over 28 million airSlate SignNow users

Sign Now