This guide walks a new eSHARE customer through the full onboarding journey, from the initial handoff out of Sales through a monitored go-live and the ongoing partnership that follows. It is written for the cross-functional project team: the Executive Sponsor, Project Manager, Product Owner, and the M365, identity provider, DNS, and email administrators who complete the technical setup. Most deployments go live in 4–6 weeks across three onboarding phases, coordinated by a dedicated Customer Success Manager (CSM), who stays with you long after go-live. Your team sets the pace: internal change approvals and administrator availability are the biggest factors in how quickly you move.
REQUIREMENT:
Before Phase 1 begins, your organization must name a Project Sponsor, Project Manager, and Product Owner, and identify your M365, identity provider, and DNS administrators. See Prepare Before Kickoff below for the full readiness checklist.
Implementation Roadmap
Every step on one map, from planning through ongoing success. Your CSM confirms during Pre-flight Planning which tracks apply, so Secure Email and optional steps only appear if they fit your environment. Step numbers in the diagram match the steps in the phase sections below.
.png?sv=2026-02-06&spr=https&st=2026-11-18T19%3A58%3A36Z&se=2026-11-18T20%3A20%3A36Z&sr=b&sp=r&sig=C%2BSUpZN5tkkrNwtnTXvR8JmNeS40UOqiuWPvUklYrtA%3D)
Customer — your team leads · eSHARE — eSHARE handles it · Both — shared working session
4–6 weeks to go-live (Phases 1–3) is typical when approvals and administrators are lined up early. eSHARE is ready to move at your speed; the overall timeline depends on your internal change processes. Phase 4 then continues for as long as you use eSHARE.
How We Work Together
Three recurring touchpoints run through the whole engagement:
Weekly check-in — a recurring status, milestone, and escalation meeting hosted in eSHARE's Microsoft Teams, with Copilot capturing notes and action items.
Installation sessions — dedicated technical working sessions with your administrators for each configuration step.
Project Trusted Share — a secure eSHARE Trusted Share for exchanging questionnaires, templates, and project documents. Confirm who needs access at kickoff.
Build Your Project Team
A successful deployment needs a cross-functional team. Name these people before kickoff and share this guide with each of them so every team knows which steps it owns.
Customer role | What they do | Needed in steps |
|---|---|---|
Executive Sponsor | Sets strategic direction, funds the project, sponsors adoption, and handles high-level escalations. | 4, 27, escalations |
Project Sponsor | Owns the business case, approves scope and major changes, and keeps executives aligned. | 2, 4, 27 |
Project Manager | Plans the timeline, coordinates tasks, tracks milestones, and manages risks and open issues. | 2–4, 9, 22, 24–25 |
Product Owner / Technical Lead | Defines use cases, validates configuration, links business and technical teams, and signs off deliverables. | 2–4, 6, 10, 15, 17, 21–28 |
Change Management & Adoption Lead | Drives adoption strategy, internal communications, super-user coordination, and adoption metrics. | 22–23, 25–27 |
eSHARE Administrator | Runs eSHARE after deployment: user access and permissions. Completes admin training. | 10, 14–17, 21, 26, 28 |
M365 Global or Application Admin | Manages tenant-level Microsoft 365 settings, approves third-party integrations, and grants Graph consent. | 8, 11–13 |
IdP Administrator | Configures SSO (SAML or OIDC), manages user provisioning, and validates sign-in flows. | 8, 11 |
DNS Administrator | Creates CNAME and DNS records for eSHARE domains, working with the Email and M365 admins. | 5, 8 |
Email Administrator / Architect | Owns SPF, DKIM, and DMARC records, mail routing, and allowlisting. Essential for Secure Email. | 5, 15–16 |
Change Advisory Board | Approves change requests through your internal ITSM process before production changes. | 9 |
Azure or SIEM Administrator | Provisions Azure SQL and Blob storage, or connects your SIEM. Only if these optional steps apply. | 18, 20 |
Your eSHARE team
Customer Success Manager — your day-to-day lead. Drives configuration and adoption strategy, and stays your relationship owner after go-live.
Project Manager — runs delivery end to end, tracks milestones, and flags and mitigates risks.
Platform Architect — leads the technical architecture review with scalability and best-practice guidance.
Sales Engineer — carries pre-sales technical context into delivery and confirms the architecture design.
Account Executive — manages the commercial relationship, new use cases, and licensing.
Executive & Project Sponsors — own delivery accountability on the eSHARE side and unblock high-impact issues.
Prepare Before Kickoff
Work through the required items before Phase 1 begins. Items under “If it applies” can wait until your CSM confirms they are in scope.
Note:
Start your change approvals now. Your change process sets the pace of the whole deployment. If your organization uses a Change Advisory Board, open that process in parallel with planning and share your typical lead time with your CSM so it is built into the plan from day one.
Required before you start
Name the Project Sponsor, Project Manager, and Product Owner.
Identify your M365, IdP, and DNS administrators and confirm their access rights.
Complete your order paperwork so the project can be scheduled.
Block calendars for Pre-flight Planning and the Project Kickoff.
Open your change-approval process and note its lead time.
Note any change-freeze or blackout windows.
If it applies
Nominate a Change Management & Adoption Lead and super-users.
Pick a small group of internal test users for policy validation.
Gather the branding assets listed in the tenant setup requirements.
Document your Microsoft Purview sensitivity-label scheme.
Deploying Secure Email? Involve your Email Administrator from the start.
Secure Conversations or SIEM? Line up Azure and SIEM admin access.
Technical prerequisites — your administrators validate these with the CSM in step 8. Your CSM provides the full Technical Prerequisites document and change request templates.
Component | Requirement | Required role |
|---|---|---|
DNS entries | CNAME records for your vanity and Share-With-Me domains. SPF, DKIM, and DMARC entries for Branded Mail. | DNS Admin, Email Admin |
SSO (SAML 2.0) | An eSHARE SAML application in Entra ID Enterprise Applications, or your IdP, for seamless portal sign-in. | Global or Application Admin, or IdP Admin |
Entra ID app registration | A custom eSHARE app with a modified manifest, using public certificates or eSHARE-provided self-signed ones. Used only for service-to-tenant communication. | Global or Application Admin |
Microsoft Graph permissions | API permissions that let eSHARE integrate with OneDrive, SharePoint, Teams, and sensitivity labels. | Global Admin, eSHARE Admin |
Trusted Sharing apps | The Action Menu app as an Enterprise Application, and the Trusted Sharing app from the Microsoft 365 store, each with Graph consent. | Global Admin, or SharePoint & Teams Admin |
Network allowlisting | Allowlist eSHARE service URLs on network appliances such as CASB, IDS, firewall, and proxy. | Network and system admins |
Azure SQL and Blob storage | Optional. MySQL or Azure SQL for Secure Conversations text, and Blob storage for inline images in secure email and conversations. | Azure Subscription Owner or Contributor |
Tenant setup requirements — gather these values and send them to your CSM through the project Trusted Share ahead of steps 5 and 6.
Setting | What to provide | Example |
|---|---|---|
Vanity domain | The branded URL for your secure Collaboration Web Portal. | share.yourcompany.com |
Share-With-Me domain | The domain used for Share-With-Me links. | sendto.yourcompany.com |
Authentication type | The single sign-on method through your identity provider. | SAML 2.0 with Microsoft Entra ID |
Notification sender | The address used for system alerts and sharing notifications. | no-reply@yourcompany.com |
Logo files | 200 × 50 px PNG with a transparent background, in full-color and white (reversed) versions. | logo-color.png and logo-white.png |
Brand background color | The hex code for your primary brand color. | #006BD6 |
Follow the steps in order and check each “Done when” before moving on. Your eSHARE Project Manager keeps the master project plan and confirms dates with you.
Phase 1: Initiation
About 1 week.
eSHARE hands your proof-of-concept context from Sales to Customer Success. Your team agrees scope and documents the current environment.
Internal transition — eSHARE · before kickoff. eSHARE Sales hands your proof-of-concept results and context to Customer Success. Who's needed: eSHARE only. No action needed. Done when: your CSM is assigned and reaches out.
Pre-flight planning — Both · 1 hour. Align on scope, participants, governance, and meeting cadence. Optional tracks are scoped in or out here. Who's needed: Product Owner, Project Manager. Done when: scope, milestone dates, and participants agreed.
Deployment survey — Customer · 2–3 hours. Complete the Pre-Deployment Questionnaire covering Microsoft 365, identity provider, DNS, and email setup. Who's needed: Product Owner, Project Manager. Done when: questionnaire returned to your CSM.
Phase 2: Implementation
Typically 2–4 weeks.
Foundations go in (domains, DNS, tenant, approvals), eSHARE connects to Microsoft 365, and policies are configured, tested, and handed to trained admins.
Core setup
Project kickoff — Both · 1 hour. Confirm owners and governance, receive the project plan, and set up weekly check-ins and the project Trusted Share. Who's needed: all project team members. Done when: plan shared; recurring meetings scheduled.
Domain & DNS — Customer · 1–2 hours, plus propagation. Choose your vanity, Share-With-Me, and notification domains and confirm user sign-in names (UPNs). Once your change request is approved, add the CNAME, SPF, DKIM, and DMARC values your CSM provides. Allow 24–48 hours to propagate. Who's needed: DNS Admin, Email Admin. Done when: domains confirmed; records validated by your CSM.
Branding files — Customer · 30 minutes. Share your logo, colors, and fonts following the tenant setup requirements and branding guidelines. Who's needed: Product Owner, Marketing. Done when: branding files delivered. See Branding guidelines.
Tenant provisioning — eSHARE · 2–3 business days. eSHARE registers your tenant, applies your branding, and creates baseline sharing policies. Who's needed: eSHARE only. No action needed. Done when: your CSM confirms the tenant is ready.
Prerequisites review — Both · 1–2 hours. Validate every technical prerequisite with your CSM and close any open questions. Who's needed: DNS, M365 Global or Application, and IdP Admins. Done when: prerequisites validated; tentative sign-off secured. See Setup and prerequisites.
Change request — Customer · varies by your process. Submit change requests through your ITSM process before production changes. Start early: approvals are the most common cause of slippage. Who's needed: Project Manager, Change Advisory Board. Done when: change requests approved.
Use case & policy workshop — Both · 1.5–2 hours. Align sharing policies to your governance goals and how your teams really collaborate. Guardrails, not barriers. Who's needed: Product Owner, eSHARE Admin, core team. Done when: use cases and policy approach documented. See Sharing policy options.
Collaborate
SSO configuration — Customer · 1–2 hours. Configure SAML or OIDC in your identity provider, send the SAML metadata to eSHARE, and test sign-in. Who's needed: Application or Global Admin, or IdP Admin. Done when: a test user signs in through SSO. See SSO configuration.
Cloud storage authorization — Customer · 1–2 hours. Link SharePoint and OneDrive through a service principal and grant read access to Purview (MIP) labels, users, and groups. Purview DLP sync is optional. Who's needed: Application or Global Admin. Done when: eSHARE reads your storage, labels, users, and groups. See Entra ID app registration.
M365 app & Action Menu install — Customer · 30–60 minutes. Install the Trusted Sharing app from the Microsoft 365 store and the Action Menu as an Enterprise Application. Who's needed: SharePoint & Teams Admin, or Global Admin. Done when: both apps installed and working. See Install M365 applications.
Tenant & policy configuration — Both · 2–3 hours. Onboard admins, set cloud providers, apply the workshop policies, finish Share-With-Me setup, and map MIP labels. Who's needed: eSHARE Admin. Done when: settings, policies, and label mapping validated. See Admin Console.
Secure Email — only if you are deploying the Secure Collaboration Gateway
Email architecture review — Both · 1–1.5 hours. Identify integration points and use cases for the eSHARE Secure Collaboration Gateway (SCG). Who's needed: Product Owner, Email Admin or Architect, eSHARE Admin. Done when: use cases and integration points agreed.
Email configuration — Customer · 1–2 hours. Create inbound and outbound connectors that route mail through the eSHARE Secure Mail Gateway. Who's needed: Email Admin, eSHARE Admin. Done when: mail routes correctly for the agreed use cases. See Install the Secure Collaboration Gateway.
Additional
Policy validation — Both · 2–4 hours over a few days. Test policies with the core team and a small group of internal test users. Final adjustments happen here. Who's needed: Product Owner, eSHARE Admin, core team. Done when: test users confirm expected behavior.
SQL & blob storage (optional) — Customer · 1–2 hours. For Secure Conversations: MySQL or Azure SQL for message text and Azure Blob Storage for inline images. Who's needed: Azure Subscription Owner or Contributor. Done when: database and storage connected. See Secure Conversations.
Power BI reporting — Both · 30-minute walkthrough. eSHARE provisions an events and audit-log report, in the eSHARE tenant or yours, and walks your users through it. Who's needed: eSHARE; Application or Global Admin if hosted in your tenant. Done when: nominated users can access the report. See Power BI dashboards.
SIEM integration (optional) — Customer · 1–2 hours. Stream eSHARE event and audit data into your SIEM alongside your wider security telemetry. Who's needed: SIEM Admin. Done when: eSHARE events appear in your SIEM. See Stream events to Azure Event Hubs.
Admin training — Both · 1.5–2 hours. A live, recorded session on administration, configuration, user provisioning, and support workflows. Who's needed: eSHARE Admins, Product Owner. Done when: admins attended or watched the recording. See Admin documentation.
Phase 3: Go Live
About 1 week, then a monitored launch.
eSHARE moves to production and users come on board. Customer Success monitors the first 2–4 weeks closely.
Onboarding & communication plan — Both · 1–2 hours. Agree the rollout sequence, messaging, training materials, and channels for a coordinated launch. Who's needed: Product Owner, Project Manager, Adoption Lead. Done when: comms plan and support materials finalized.
End-user training — Both · 1 hour per session. Live sessions on secure file sharing, guest access, and the Microsoft 365 integration. Who's needed: end users; Adoption Lead coordinates. Done when: scheduled sessions delivered. See Getting started.
Service go live — Both · milestone. eSHARE formally moves to production and Customer Success confirms the agreed success criteria. Who's needed: Product Owner, Project Manager. Done when: live in production; success criteria confirmed.
End-user onboarding — Both · ongoing; first 2–4 weeks monitored. Onboard users in waves per the rollout plan while Customer Success monitors the launch period. Who's needed: Product Owner, Project Manager. Done when: launch period closes with no open blockers.
Phase 4: Ongoing Success
Continues after onboarding.
Onboarding ends, but the partnership does not. Regular check-ins and business reviews keep adoption growing, and help is there whenever new needs come up.
Monthly CS check-in — Both · 30–60 minutes, monthly. A regular session with your CSM to review adoption and usage, open requests, and upcoming changes in your environment. Who's needed: Product Owner, eSHARE Admin; Adoption Lead as needed. Done when: usage reviewed and next month's actions agreed.
Quarterly business review (QBR) — Both · 1 hour, quarterly. Step back with your CSM and Account Executive to review outcomes against your success criteria, adoption trends, and the eSHARE roadmap, and to plan new use cases. Who's needed: Executive or Project Sponsor, Product Owner, Adoption Lead. Done when: outcomes reviewed and priorities set for the next quarter.
Ad-hoc support & requests — Both · as needed. Raise support issues, configuration or policy changes, and new use case ideas as they arise. Your CSM routes each request and keeps you updated. Who's needed: eSHARE Admin or any project team member. Done when: request resolved or scheduled, with progress shared. See Contact eSHARE Support or Contact eSHARE Gov Support.
Getting Help
You are never on your own during onboarding. Your CSM shares direct contact details at kickoff.
Your Customer Success Manager — assigned before kickoff. Your single point of contact for scheduling, templates, and configuration questions, during onboarding and after go-live.
eSHARE Project Manager — tracks milestones and risks, and runs the weekly check-in with your project team.
Project Trusted Share — the secure space where questionnaires, templates, and project documents are exchanged throughout onboarding.
Weekly check-in — the standing forum for status updates, decisions, and escalations, with notes and action items captured for everyone.
Training sessions — admin and end-user sessions are scheduled with you during Implementation and Go Live. Admin training is recorded.
Documentation — docs.eshare.com has step-by-step articles for each configuration task in this guide.
Contact support — for technical issues, configuration questions, or service requests at any stage, open a ticket with the support team for your environment.
eSHARE Support — for commercial eSHARE customers. Submit a request.
eSHARE Gov Support — for eSHARE Gov customers. Submit a request.