MSIX requires packages to be signed in order to be deployed. This helps us to offer integrity on the package being deployed and to ensure the contents being deployed are what was packaged from the d...
Updated Mar 03, 2022
Version 3.0
Blog Post
There was something missing from my SDK installation (appxsip.dll), I reinstalled the SDK with most components enabled and now I'm able to sign the MSIX package. Also learned 2 other things during my journey getting DGS running:
- Getting the Azure AD Access Token with the Powershell script doesn't work when your account has Azure MFA enabled. In the latest version (October 2019) of the MSIX Packaging Tool this does work, so that's nice!
- Filled in the wrong CN in the Certificate, the CN is the same as the Tenant Name. This was not very clear to me in the article. In the latest version of the MISX Signing Tool it automatically fills in the CN, so that's also a very nice feature of the latest version!