Azure ARM. Nested deployment fails to deploy content

Question

It has been months already since I have been trying to implement and deploy a IaC template for Azure Logic Apps. The playbook I'm trying to deploy is based on a custom connector which I would like to deploy together with the playbook itself using nested deployment.

{
      "type": "Microsoft.Resources/deployments",
      "apiVersion": "2021-04-01",
      "name": "custom_connector_template_link",
      "dependsOn": [],
      "properties": {
        "mode": "Incremental",
        "templateLink": {
          "relativePath": "custom_connector/template.json"
        }
      }
    }	

This short piece of code should get job done but unfortunately it doesn't. Indeed, when starting the deployment through Azure DevOps, it shows the following:

[Warning] Skipping deployment for D:\a\1\s\UAT\Playbook\get_geo_from_ip\azuredeploy.json. The file contains resources for content that was not selected for deployment. Please add content type to connection if you want this file to be deployed.

One might think that is the nested template the root cause, but it is not because I deployed it as a standalone component.

Also, I receive the same warning when I try to deploy automation rules templates.

If you need more information, just let know. I'll be really glad to receive your help.

Answer 1

Hello, @Jacopo Terrinoni - Thanks for reaching out! Definitely no fun having been blocked with a technical issue for that long. I've looked into this a bit, and on the surface, the issue seems more about Sentinel and CI/CD than it is about Logic Apps and its Custom Connector resources. I'll continue to dig deeper, ask my peers who work on Sentinel, and share my findings with you here but if you're able to share more specific details about your ARM setup and general info on what you're trying to accomplish/end goal, that'll surely help us as well.