After sign-in to vs code, an environment must be created or the existing environment can be used. By creating an environment the URL to GitHub repository can be enter in the Git Repository field. The git is cloned in workspace once the IDE is hosted.
For the next time is not necessary to create an environment again, and the existing one can be used.
I used the following tooling or extensions on the vs code online:
I installed the power shell 7 and developer the power shell scripts.
Connected the IDE to Azure and executed the power shell scripts.
I installed the azcli extension and developed the .azcli scipts.
Docker is available by default on the IDE machine.
I installed the docker-composer and ran the docker-composer file.
Installed the Azure App Service extension and deployed the docker image from local on the Azure App Service.
Most organizations choose to work with multiple cloud providers, because it’s a struggle for an enterprise to find only one public cloud infrustructure provider, which meet all their requirements. [refrence]
The following figure demonstrates that the multi-cloud solution is a sub concept for hybrid-cloud computing.
The two common multi-cloud deployment scenarios are
Multi-cloud: When a service or product runs on more than one cloud service provider infrastructure. Multi-cloud scenarios are using the partitioned multi-cloud pattern.
Intercloud: When data is integrated or exchanged between cloud service providers as part of a logical application deployment.
1-Strategic advantages of partitioned complexity
To avoid committing to a single vendor, you spread applications across multiple cloud providers. Best Practice:weight the strategic advantages of a partitioned complexity this setup brings. Achieving workload portability and consistent tooling across multiple cloud environments increases development, testing, and operations work. 
2-For regulatory reasons
For regulatory reasons, you serve a certain segment of your user base and data from a country where a vendor does not yet have any presence. Best Practice:Use a multi-cloud environment only for mission-critical workloads or if, for legal or regulatory reasons, a single public cloud environment cannot accommodate the workloads. 
3-Choose the best services that the providers offer
For deploying application across multiple cloud providers in a way that allows you to choose among the best services that the providers offer. Best practice:Minimize dependencies between systems are running in different public cloud environments, particularly when communication is handled synchronously. These dependencies can slow performance and decrease overall availability. 
4-To have data autonomy
To have data autonomy in the future, therefore companies can take their data with them wherever they end up going.
Advantage of multi-cloud scenarios
To avoid vendor lock-in. The multi-cloud helps lower strategic risk and provides you with the flexibility to change plans or partnerships later. 
If the workload has been kept portable, you can optimize your operations by shifting workloads between computing environments. 
Hybrid-cloud description by National Institute of Standards
Hybrid cloud is a composition of two or more distinct cloud infrastructures (private, community, or public) that remain unique entities, but are bound together by standardized or proprietary technology that enables data and application portability. 
Cloud and on-premises, which were previously distinct entities and had cumbersome interaction configuration, are now converging to provide more efficient, less costly, and more flexible operation model for workflows.
1-Backup & Archive 
2-Data Protection 
3-Lifecycle Partitioning 
Lifecycle partitioning is the process of moving parts of the application development lifecycle to the cloud while the rest remains on premises. The most popular is the cloud deployment and testing but move to on-premises for the production deployment.
4-Application Partitioning 
A part of an application is running in the could and the other part runs on premises. For example, Sony PlayStation runs databases for individual games in the cloud but takes care of user authentication on-premises.
5-Application spanning 
Application spanning happens when the same application runs on-premises and in the cloud. “Best Buy” is an example of the application spanning. The entire online store application is running across multiple cloud regions and multiple on-premises data center to allow it to quickly adjust to demand.
Nowadays, developers, enterprises, and organisations often create open Application Programming Interfaces (APIs) that allow other teams, developers, customers, and services to integrate to their products and services.
The following figure demonstrates the API lifecycle and after the Deploy phase the API can be shared with other API’s consumers in the Share Phase.
Today is usual to share the APIs via API Management and each cloud provider has its own API Management solution for a better API management and API monitoring. more…
In API Management each API has its own endpoint.
Request is sent to API endpoint in API management.
The above request is passed to the Backend API via API management.
The request is processed in the backend API and if necessary the data layer is used and the result is generated
The response, which contains the result, is sent back to the API management.
The API management sends the response to the caller.
Application Programming Interface Management (API Management), consists of a set of tools and services that enable developers and companies to build, analyse, operate, and scale APIs in secure environment.
API Management Service
Amazon API Gateway
– API Gateway – Developer Portal
– API Access Control – API Protection – API Creation and design – Support for hybrid models – High performance – Customizable developer portal
API Management tools overview
API Management can be delivered on-premises, through the could, or using a hybrid on-premises – SaaS (Software as a Service) approach.