this version is reworked for the final Container Apps namespace Microsoft.App This week virtual network integration and with that a bring-your-own virtual network capability was made available for Container App Environments: https://techcommunity.microsoft.com/t5/apps-on-azure-blog/azure-container-apps-virtual-network-integration/ba-p/3096932 As mentioned in my Container Apps post last week this virtual network integration is elementary in my scenario…

Azure private link / endpoints allow you to connect resources to your private virtual network and with that — when removing public access — shield resources from being accessed or even attacked from the internet. …

We are using Private Linking — as described here — in multiple scenarios, globally distributed: Regular deployments are usually handled by build agents in those isolated regional networks which (😀 of course only for emergency debugging) also can be used as jump boxes. This can make some out-of-the-ordinary maintenance jobs…

ACME brings a high level of convenience for issuing certificates for cloud services (global & local gateways, web services). That works pretty fine in many variations, but what if I don’t have an actual server where I can host some certbot / nginx magic to handle a HTTP-01 challenge —…