When a new SSIS connection manager appears after deployment from Visual Studio but not after a pipeline release, inspect the pipeline’s .ispac before changing SSISDB. In the project deployment model, the built project file is the deployment unit; a successful pipeline can still publish an old or incomplete artifact.
Last updated: November 19, 2026.
$ispac = Resolve-Path '.\bin\Development\Orders.ispac'
$work = Join-Path $env:TEMP ([guid]::NewGuid().ToString())
New-Item -ItemType Directory -Path $work | Out-Null
Copy-Item $ispac (Join-Path $work 'project.zip')
Expand-Archive (Join-Path $work 'project.zip') -DestinationPath $work
Get-ChildItem $work -Recurse -File | Select-Object Name, Length
Select-String -Path (Join-Path $work '@Project.manifest') -Pattern 'OrdersDatabase' -SimpleMatchReplace the project and connection names with yours. Preserve the original .ispac; the copied ZIP is only for inspection. If the connection is absent here, deploying the same artifact again cannot make it appear in SSISDB.
Confirm what the pipeline actually built
Microsoft’s SSIS deployment documentation states that a project is built into a self-contained .ispac and that the project, not an individual source .dtsx file, is deployed to SSISDB. Record the artifact path and hash from the build stage, then verify that the release stage downloads and deploys that exact file.
Check that the connection-manager source file is committed, included in the .dtproj, and present in the clean build workspace. Delete stale pipeline output before building. A locally generated artifact and a pipeline artifact with different manifests are different inputs, even when both deployments report success.
Match the connection scope to the deployment model
Microsoft documents that shared project connection managers require the project deployment model. If the connection must be visible and configurable across packages, create it under the project’s Connection Managers node and make packages reference that project connection. A package-only connection remains part of its package and should not be mistaken for a missing project-level object.
After the artifact passes inspection, deploy it directly once and check the project configuration in SSISDB. Environment references and parameter mappings supply values to objects already present in the deployed project; they do not add a connection manager omitted during the build. Keep the verified artifact and build log so later releases can compare hashes and manifest contents.