Your infrastructure needs replacing
Use the hardware refresh to review capacity, supported versions, connectivity, security and the cost of operating the environment.
WyldLynx / Content Manager hosting
Content Manager hosting in Azure
Plan the environment and the people who will run it.
Work with Content Manager engineers to assess an Azure environment. Agree the hosting model, operational responsibilities, security, recovery and support around the way your organisation uses its records.
Give Content Manager a planned home in Azure
Ageing servers, a growing dataset or a cloud migration can make it time to review where Content Manager runs. The application, database, document stores, search and integrations need to be considered together.
WyldLynx works with your team to design and operate a Content Manager environment in Microsoft Azure. Agree what is managed, who owns each responsibility and how the service will be reviewed before moving production records.
When a hosting review is useful
The specialist knowledge is stretched
Identify which tasks need Content Manager engineering, which stay with your own team and how support is coordinated.
Content Manager is part of a cloud programme
Assess the application and its connected systems alongside the organisation's Azure policies and records requirements.
What the managed service should cover
Use these areas to define the proposal and division of responsibilities. They are a scoping checklist, rather than a promise that every item is included in every plan.
| Area | What to plan and confirm |
|---|---|
| Environment design | Size production and test environments from the dataset, user numbers, document volumes, integrations and performance requirements. Agree any development environment. |
| Azure foundation | Agree the subscription, region, network design and connectivity. Record the locations of production data, backups, recovery copies, logs and any external processing. |
| Content Manager components | Plan workgroup services, event processing, document storage, rendering and client access around the supported product version and architecture. |
| Database and search | Confirm the supported database and search deployment, capacity and maintenance responsibilities for the selected release. Read about cloud deployment performance. |
| Integrations and identity | Test the required Office, Outlook, Microsoft 365 and business-system connections. Agree identity, authentication, administrative access and permissions for the design. |
| Security operation | Document encryption, patching, logging, alerting and access responsibilities. Product configuration and the service's agreed security scope need their own evidence. |
| Backup and recovery | Agree backup frequency, retention, location, recovery objectives and restore testing in writing. Set out who performs the checks and how results are reported. |
| Monitoring and maintenance | Define platform and application monitoring, alert recipients, maintenance windows, escalation and reporting. Confirm business-hours and after-hours arrangements. |
| Patching and upgrades | Plan operating-system, database and Content Manager changes. Test supported releases and integrations before an agreed production change; confirm plan inclusions and any separate work. |
| Support and reporting | Define service boundaries, response commitments, availability measures and report frequency in the agreement. Review Content Manager support options. |
Choose the subscription and operating model
WyldLynx-managed Azure
Discuss an environment operated through a WyldLynx-managed subscription. Confirm ownership, isolation, charges, access and exit arrangements in the offer.
Your Azure subscription
Discuss operation within your organisation's subscription. Agree administrative access, licensing, billing and the responsibilities retained by your cloud and security teams.
A shared operating arrangement
Your team and WyldLynx can assess a split between infrastructure and application management. Document the hand-offs so monitoring, changes and incidents have clear owners.
Move an existing environment with a tested plan
Review what is there
Record the current release, dataset, document stores, clients, integrations and access requirements. Identify support and compatibility constraints.
Build and test a copy
Use an authorised test copy to check the proposed environment, integrations, performance and user tasks. Protect test data and agree how it is removed.
Agree cutover and rollback
Plan migration, validation, downtime, communications and a fallback. Define the authoritative system at each stage to avoid conflicting writes.
Validate and hand over
Reconcile the database and document stores, test access and integrations, and confirm operational ownership before retiring the old environment.
An Azure move does not by itself guarantee faster performance or remove upgrade work. Size and test the environment against the tasks your people need to complete.
Check licensing before choosing a model
Review Content Manager entitlements alongside the database, operating system, connected products and Azure services. Confirm whether the current contracts permit the intended deployment and access pattern.
Compare the relevant perpetual, subscription and vendor-managed cloud options with the proposed hosting arrangement. Do not assume that licences transfer unchanged or that an upgrade is included. Discuss a renewal and licensing review.
Make security responsibilities explicit
WyldLynx's published information security page describes its ISO/IEC 27001:2022 information security management certification. Confirm the current certificate and scope for the proposed service. Management-system certification does not certify a product configuration or guarantee that a hosted environment meets every customer obligation.
Record the approved regions, data flows, access controls, recovery requirements and evidence your organisation needs. Review these with the people responsible for security and recordkeeping before the service is accepted.
Questions to put in the proposal
- Where are production records, backups, logs and recovery copies held?
- Who patches each component, and how are changes tested?
- What recovery objectives apply, and how will restore tests be evidenced?
- Which releases, clients and integrations are supported?
- Who receives alerts and handles incidents outside business hours?
- What certification scope, service reports and access records will be available?
- What charges, data handover and exit arrangements apply?
Use the answers to compare proposals and agree the service. Avoid relying on an assumption that an infrastructure service includes application management.
Common questions
Can you operate Content Manager in our Azure subscription?
We can assess that model with your cloud and security teams. Agree subscription ownership, administrative access, licensing, charges and the division of responsibilities in the proposal.
Where will our records and backups be held?
The approved production, backup and recovery locations must be named in the service agreement. Confirm all relevant data flows and any cross-region replication before deployment.
How does this differ from OpenText Content Manager Cloud?
A vendor-managed cloud service and a partner-managed Azure environment can differ in contracts, deployment, operation, entitlements and customer responsibilities. Compare the current offers against your requirements before choosing.
Which versions do you host?
Confirm the supported release, clients, database, search and integrations for the proposed design. An older environment may need upgrade or remediation work before migration.
What does it cost?
The proposal should separate design and migration work, ongoing management, Azure consumption, licences and any additional support. Pricing and inclusions are agreed for the environment.
What happens if we leave?
Agree ownership, access, export formats, documentation, handover assistance, charges and timeframes in the contract. These terms should be clear before the service begins.
Tell us about your Content Manager environment
Tell us the version, user numbers, dataset size, where it runs today and what concerns your team. We can discuss a suitable assessment and the information needed for a hosting proposal.
Return to the Content Manager hub or review support options.