An organization has started to develop cloud-native applications to replace their legacy applications. What else should the organization do to adopt the cloud?

Providing privileged cloud network access to third-party partners introduces unnecessary security risks and is not a standard step in cloud adoption strategy.

Cloud adoption is a holistic journey that includes both developing new cloud-native applications and lifting or refactoring legacy systems into cloud-hosted infrastructure. Migrating legacy infrastructure reduces reliance on on-premises hardware, enables scalability, and aligns the organization's entire portfolio with cloud capabilities. Leaving legacy infrastructure on-premises creates a fragmented hybrid environment that limits the full benefits of cloud adoption.

Conducting maintenance on legacy hardware sustains on-premises dependency and works against the goal of cloud migration and adoption.

Increasing capital expenditure (CapEx) on existing projects contradicts the cloud model, which shifts spending from CapEx to operational expenditure (OpEx).