 Background: A global firm embarked on a NAME_1 migration journey 4 years ago, on the assumption that a blanket-approach adoption of NAME_1 across all its local companies would allow the firm to realize the benefits of NAME_1 including scalability and flexibility to cope with business expansion. That strategy is not without flaw, by imposing a target date without a thorough understanding of the complexity of existing IT landscape, many applications simply take a 'lift-and-shift' approach instead of exploiting the full potential of NAME_1 benefits. Furthermore, not all legacy systems are suitable for NAME_1 migration: when considering the ROI and the state of these systems when many remain fully operational, their lifespans could have been extended through careful modernization initiatives. That said, the group's revised strategy is as such:
NAME_1 Native and NAME_2. 
Multi-NAME_1 providers - Azure and GCP
Flexible adoption of NAME_1. Mixed environment with on-prem and NAME_1 applications, instead of aiming for a 100% NAME_1 adoption.
Strengthen NAME_1 governance as in cost control and optimization.

The local constraints are:
Not all systems are suitable migrating to NAME_1 due to its legacy nature and economic justifications. A recent suitability assessment has been conducted with mixed results
Use of GCP is not without issue given the local company's geo-location where Goggle is not allowed to operate.
Hybrid NAME_1 approach is generally welcomed
The company suffers from poor project prioritization process, complicated by the fact that senior stakeholders do not understand the benefits of NAME_1, as a result priorities are biased towards short term benefits as opposed to adoption of seemingly far-fetched goals irrelevant to the business departments. instruction 1: create a paragraphs on hybrid-NAME_1 approach and emphasis on the  use of GCP given the local company's intricate business revenue derived largely from a geo-location where Goggle is not allowed to operate. Provide exactly two different responses that are separated with 6 asterisk symbols: ******.
user