Application and audience
Document the public website, internal application or data service you need to host. Estimate usage, accessibility needs, peak demand and dependencies on other systems.
Define the application, procurement and operating requirements before selecting a dedicated or cloud server.
Document the public website, internal application or data service you need to host. Estimate usage, accessibility needs, peak demand and dependencies on other systems.
Record approved hosting locations, administrator roles, retention requirements and restrictions on access. Confirm the evidence your organization needs; a location label is not proof of compliance.
Compare the published configuration and total with your purchasing requirements. Review service terms, operating responsibilities and any evidence required by your procurement process.
Assign ownership of monitoring, backups and incident response. Test restoration and document recovery priorities for each application rather than treating all workloads as identical.
Use a test environment to check software compatibility, integration, performance and recovery. Confirm that the selected service meets your organization’s requirements before moving production data, including any specific documentation your procurement team needs.
Follow the deployment and migration checklist, and review management responsibilities with the team that will operate the server.
Compare configurations and prices, then review your selected options in the cart.