After generating the sources of the application you may deploy the generated sources to Git, compile / package and then deploy the packages to Azure Artifacts, or compile/package and deploy to the target environment.
You could extend GeneXus and create your own ‘Deployment target’ for deploying sources.
This part of GeneXus is extensible, and in the genexuslabs space are other deployment targets provided as open source so that you can create your own: https://github.com/genexuslabs/deployment-targets
Use https://wiki.genexus.com/commwiki/servlet/wiki?42073,Application+Deployment+MSBuild+tasks
Note: For this, you use the same options as described in section ‘Package and Deploy App to Target Environment’, but selection ‘OnlyPackage’.
With that, you get the package.
After that, you can upload it to Azure Artifacts, and for this, you could also create your own Deployment Target https://github.com/genexuslabs/deployment-targets
If you package and deploy an Angular App and a .NET Backend
- Deploy Backend to APIM & Azure Functions https://wiki.genexus.com/commwiki/servlet/wiki?49957,Deploy+mobile+services+to+Azure+Serverless+using+API+Management+%28GeneXus+17+upgrade+8%29,
- Deploy Angular Frontend to Azure Object Storage (Azure Storage Static Websites) https://wiki.genexus.com/commwiki/servlet/wiki?49878,Deploy+Front-end+applications+to+Azure+Blob+Storage
- https://wiki.genexus.com/commwiki/servlet/wiki?49887,Build+and+deploy+a+static+website+to+Azure+Storage+Static+Websites%3A+setting+up+the+cloud,
If you package and deploy a .NET Web app or Web Service to Azure Web App
- https://wiki.genexus.com/commwiki/servlet/wiki?31457,Deploy+as+Azure+Web+App
Other options (Functions triggered by Service Bus, HTTP, etc, ): https://wiki.genexus.com/commwiki/servlet/wiki?32092,Toc%3AApplication+Deployment+tool,