Reassign technical tasks when changing hosting
A managed service can take on operational tasks. Still check who specifically manages accounts, project access, keys and the handover.
A new hosting provider can take on certain operational tasks and relieve your team. Which tasks actually transfer depends on the chosen service and its agreed scope. Responsibilities for your own application must remain specific.
Microsoft distinguishes technical tasks by service model and describes the data, identities and access that still need management. Use this technical division as a starting point for handing over your specific service.
An inherited account remains an application decision
In a fictional design, a customer portal moves to a managed platform. Existing project memberships are carried over. In the example, account U-65 is still assigned to a project although its access should end. The new provider has supplied the platform; the application would continue evaluating the inherited membership.
A different location does not automatically correct this record. The team needs a decision about membership and its effective implementation in the application.
Hand over tasks with a verifiable outcome
The following planning structure makes task and outcome visible for this design.
Task | Clarify at handover | Useful evidence |
|---|---|---|
Update the platform | Which layers does the specific service maintain, and which remain with the team? | Named service scope, contact and process for required changes. |
Manage project memberships | Who decides on access and who implements the change? | Permitted access works; revoked access is denied in the test. |
Replace technical credentials | Which connection uses which access, and who changes it over? | The new access works; the old one is no longer accepted after confirmed completion. |
A blanket line saying “security with the provider” leaves these outcomes open. The company can delegate tasks to a service provider. The scope, access and managed workflow must be named; a contact alone does not prove a change has been implemented.
Manage the transition through to completion
Check access to hosting administration separately from accounts inside the portal. Removing access to the old hosting console does not revoke an independent project membership. Conversely, prematurely disabling technical access that is still needed can interrupt an ongoing transition.
Record when old access is no longer needed, who removes it and how the outcome is checked. The relief provided by managed infrastructure can then be compared with the tasks that remain.
Sources
Read more
All articles
Cloud & Operations with ASES
Hosting, deployment, maintenance and support