Cisco Duo Security Sentinel - Marketplace/Content Hub install fails: location parameter is empty (minLength: 1) after Solution V3 packaging

[prajval-um]

Describe the bug
I am a developer at Cisco, and our customers are facing an issue while installing the Duo Connector for Sentinel from the Microsoft Sentinel solutions marketplace. I am experiencing the same issue. The package validates successfully before upload, and the deployment works when I deploy the same [mainTemplate.json] using Custom deployment. However, after publishing the solution, installing it from Content Hub / Marketplace fails with a location validation error (minLength: 1).

{
  "code": "InvalidTemplate",
  "message": "Deployment template validation failed: 'The provided value for the template parameter 'location' is not valid. Length of the value should be greater than or equal to '1'. Please see https://aka.ms/arm-syntax-parameters for usage details.'."
}

This happens even though:

• The solution deploys successfully when running the same [mainTemplate.json] via custom deployment (manual ARM deployment).
• The packaging/upload/publish step does not show any errors, but installation from Content Hub/Marketplace fails.

Impact: published solution cannot be installed through the normal marketplace/Content Hub flow due to location being passed as an empty string.

To Reproduce
Steps to reproduce the behavior:

1. In Azure Portal, go to Microsoft Sentinel -> Content hub.
2. Select the published solution and click Install.
3. Installation fails during ARM template validation with the error shown above: template parameter location has length < 1.

Expected behavior
The install flow should always pass a non-empty location parameter (or the template engine should fall back to resourceGroup().location), so the solution installs successfully from Content Hub/Marketplace, the same way it installs via custom deployment.

Screenshots

• Add screenshot of the Azure Portal install failure showing the InvalidTemplate / location minLength error.
• 

Desktop (please complete the following information):

• OS: macOS
• Browser: Chrome
• Version: N/A

Smartphone (please complete the following information):

• Device: N/A
• OS: N/A
• Browser: N/A
• Version: N/A

Additional context

• The issue appears only in the published install flow; direct ARM “custom deployment” works.

• Error indicates the location parameter is being passed as an empty string during the marketplace/Content Hub install.

• In the generated templates, location typically has minLength: 1. If the UI definition ([createUiDefinition.json] output uses [location()] and the portal hides/doesn’t populate it, the output can be empty and fails validation.

• Request: confirm if this is a known limitation/bug in Solution V3 packaging or portal install flow, and provide the recommended pattern to guarantee a valid location is passed during Content Hub installation (without breaking validation rules like ARM-TTK).

• Solution name (Cisco Duo Security Sentinel) and package version (3.1.0).

[v-kasghosh]

Hey @prajval-um
I tried to reproduce the issue and noticed that the latest package available in the Sentinel Content Hub for me is 3.0.2, which installed without any problems in my workspace. Let's wait for the next deployment cycle so the latest package gets updated in the Content Hub.

[prajval-um]

Hey @prajval-um I tried to reproduce the issue and noticed that the latest package available in the Sentinel Content Hub for me is 3.0.2, which installed without any problems in my workspace. Let's wait for the next deployment cycle so the latest package gets updated in the Content Hub.

Hi v-kasghosh Thanks for checking on this. Do you have an estimated timeline for when the next deployment cycle will complete? We have an urgent requirement to get this issue resolved, as our CA pinning bundle has already expired and the soft cut‑off date of 2nd February has passed.
We’ve already published the app with the new connector, and currently two connectors appear in the Content Hub:

Microsoft‑managed: Cisco Duo Security – 3.0.2 (authentication will fail because of CA pinning )
Cisco‑managed: Cisco Duo Security Sentinel – 3.1.0 (we update the support to new CA Pinning)

We have migrated from the Microsoft‑managed connector (3.0.2) to the Cisco‑managed connector (3.1.0). While the Microsoft‑managed version continues to work without issues while installing, we are encountering problems specifically with the Cisco‑managed connector. Our objective is to migrate all customers to the Cisco‑managed app, but currently customers are unable to install our connector due to this issue.
To move forward safely, we need the latest package to be available in the Content Hub as soon as possible. Any clarity on the deployment window or expected completion timeline would greatly help us plan the next steps and avoid further impact.

Additionally, I have one more question. We reused the same folder from the Microsoft‑managed application and updated all the files and necessary configurations for the new connector. Could this be causing the issue?

[v-kasghosh]

Hey @prajval-um ,

We’ve reviewed the issue and found that the solution isn’t installing correctly in the workspace and is also not appearing in the Content Hub.

The root cause is that, during publishing, the plan type was selected as Managed Application instead of the Plan Solution Template.

To resolve this, please republish the solution and make sure to select the correct plan type (Plan Solution Template) before proceeding.

For reference, please see the example screenshot below :

Thanks!

[prajval-um]

v-kasghosh Thank you for the response. Ginger will work on this and republish the app.

[v-kasghosh]

Hey @prajval-um, do you have any updates on this?

[michael-christopherson]

Just adding a +1 that we are encountering this same issue with version 3.1.0 trying to deploy new Cisco Duo Security Sentinel.