D365FO Deploy Portal v1.5.2 — Two-Level Validation, Docker Hub, Quality & Docs

We're pleased to announce D365FO Deploy Portal v1.5.2 — a release focused on deployment safety, distribution, and code quality. If you're already using the previous version (bidirectional conversion, license injection, parallel deploy, REST API), this update adds two-level deployment validation, Docker Hub availability, and a cleaner project structure.

Why Two-Level Validation Matters

When a Service Principal has access to multiple Power Platform environments, PAC CLI can connect to any of them. In the past, a misconfiguration or wrong environment selection could result in deploying a package to the wrong environment — with no immediate feedback. v1.5.2 introduces two-level validation so you always know you're deploying to the right place.

Level 1: Pre-Deploy — PAC Auth Check

Before deployment starts, Deploy Portal runs pac auth who and verifies that the current PAC session matches the target environment:

• Service Principal auth: output must contain the environment URL (e.g. target-env.crm.dynamics.com).
• Interactive auth: output may contain only Organization Friendly Name — the validator now matches on that as well.

If the session does not match the selected environment, deployment is blocked with a clear error message. No more "wrong environment" surprises.

Level 2: Post-Deploy — Log Verification

After PAC CLI finishes, the portal parses the deployment log and looks for the line "Deployment Target Organization Uri". It then checks that the actual deployment target in the log matches the expected environment URL. If they differ (e.g. you intended env A but the log shows env B), the deployment is marked as failed with a detailed message — so you can correct credentials or environment selection before the next run.

Together, these two checks significantly reduce the risk of deploying to the wrong Dataverse environment.

Docker Hub — Image and Overview

The Docker image is now published to Docker Hub as well as GitHub Container Registry:

• Docker Hub: vglu/d365fo-deploy-portal:latest and vglu/d365fo-deploy-portal:v1.5.2
• GHCR: ghcr.io/vglu/d365fo-deploy-portal:latest

The repository overview on Docker Hub is updated automatically with each release — description, usage examples, parameters, and links. No manual editing required.

Quick start (unchanged):

docker run -d -p 5000:5000 --name d365FOportal vglu/d365fo-deploy-portal:latest

Open http://localhost:5000 and start deploying.

Quality: SOLID, Unit Tests, E2E

• Interfaces: ISettingsService and ISecretProtectionService are now used across the app for settings and secret encryption — easier testing and future extensions.
• Unit tests: PackageAnalyzer, CredentialParser, deployment validators, and package update logic are covered by unit tests. Run with .\scripts\run-tests.ps1 (optionally -Coverage).
• E2E (Playwright): End-to-end tests for key flows, including Package Details (models, licenses, changelog). Run with .\scripts\run-tests.ps1 -IncludeE2E.

This release lays the groundwork for more confident changes and faster iteration.

Project Structure: Scripts in One Place

All PowerShell and helper scripts are now in the scripts/ folder. Run them from the project root:

• .\scripts\run.ps1 — development (hot reload)
• .\scripts\publish.ps1 — build self-contained Windows app
• .\scripts\check-prerequisites.ps1 — pre-flight checks
• .\scripts\Setup-ServicePrincipal.ps1 — Azure AD setup
• .\scripts\run-tests.ps1 — unit and integration tests

Documentation and internal docs are split into documents/ (user-facing, release notes) and tech-docs/ (plans, analysis, test notes) for easier navigation.

Comparison with the Previous Release

The previous major update (announced in D365FO Deploy Portal — New Version) brought:

• Bidirectional LCS↔Unified conversion
• License injection into Unified packages
• Parallel PAC CLI deployment
• Unified package merge
• Full REST API with Swagger
• CLI for headless conversion
• CI/CD pipeline integration

v1.5.2 builds on that with:

| Area | Previous | v1.5.2 | |------|----------|--------| | Deployment safety | Single-step deploy | Two-level validation (pre-deploy PAC check + post-deploy log verification) | | Distribution | GHCR + Windows ZIP | + Docker Hub image and auto-updated overview | | Code quality | — | SOLID interfaces, unit tests, E2E (Playwright), coverage support | | Project layout | Scripts in root | All scripts in scripts/; docs in documents/ and tech-docs/ |

Same product, stronger guarantees and clearer structure.

Who Benefits

• D365FO developers & release managers — two-level validation reduces the risk of deploying to the wrong environment; Docker Hub makes it easier to pull the image from any registry.
• DevOps — same REST API and CLI; plus better test coverage and script organization for custom integrations.
• Technical Delivery Managers — audit trail and validation messages make it easier to explain and correct deployment issues.

Get the Release

• Docker: docker pull vglu/d365fo-deploy-portal:1.5.2 or docker pull ghcr.io/vglu/d365fo-deploy-portal:1.5.2
• Windows ZIP: GitHub Releases — DeployPortal-1.5.2-win-x64.zip

Learn More

• D365FO Deploy Portal product page — full documentation and use cases
• GitHub repository — source, release notes, and scripts

For licensing, pricing, or a demo:

• 📧 Email: vhlu@sims-service.com
• 🌐 Website: sims-service.com

---

D365FO Deploy Portal is open-source software by SIMS tech, released under the MIT License. Source code: github.com/vglu/D365FODeployPortal