I've developed an open-source tool that creates .intunewin packages (without IntuneWinAppUtil.exe) using Node.js — I'm looking for testers with a non-production Intune tenant.
THIS IS NOT A PRODUCT PROMOTION POST, IT IS A TEST POST.
I built a small SaaS that auto-tracks new versions of Win32/macOS apps and pushes packaged updates to Intune via Graph API. The interesting bit: it generates the .intunewin format entirely in Node.js — AES-128-CBC encryption, HMAC, Detection.xml, the whole thing — without invoking IntuneWinAppUtil.exe. That lets the whole pipeline run on a Linux Docker container with no Wine, no Windows VM.
I have no Intune sandbox of my own. Microsoft 365 Developer Program rejected my application, and I don't want to risk a real customer tenant. So I'm asking here: would anyone with a non-production Intune tenant (lab, test, personal dev tenant — not a live customer) be willing to spend ~15 minutes validating one end-to-end flow?
What you'd do:
1- Register an account at <frontendtest-verpacker-app-suite-production.up.railway.app> (test deployment, marked with a banner)
2- Connect your Intune tenant (Graph API app registration with standard permissions)
3- Add a Windows app (e.g. Firefox, 7-Zip — anything in winget)
4- Trigger sync → it packages and uploads to your Intune
5- Tell me if the app appears in your Intune portal as a Win32 app ready to assign
Full step-by-step procedure with success/failure criteria is in the repo:
Validation procedure: <https://github.com/emreersoy442/verpacker-app-suite/blob/main/docs/PHASE0\_VALIDATION.md>
What I specifically need to know:
Did the Graph API commit step succeed, or did it return an error?
If it failed: the raw Graph API error body in full — please don't summarize or paraphrase. Paste the entire JSON response from the failed request. That's exactly the diagnostic data I'm missing and can't generate without a real tenant.
Important warnings:
This is a hosted test environment. Data may be reset.
Do NOT connect a production customer tenant. Use a lab/dev/test tenant only.
The .intunewin format implementation is verified against the published spec (svrooij/ContentPrep, MSEndpointMgr/IntuneWin32App) but has never been validated against the real Graph API commit endpoint — that's literally what I'm asking you to help with.