Availability and installation
Partner Portal is being prepared for Microsoft Marketplace. The published offer link will appear on the product page when available. Full Marketplace preview acquisition, artifact staging and certification remain launch requirements.
The intended installation places App Service, SQL, private document storage and Azure OpenAI resources in your Azure subscription. Azure infrastructure and AI usage charges are additional to any confirmed plan terms.
Before you deploy
- An Azure subscription and permission to create the resources and scoped role assignments required by the template.
- A supported region for Linux B1 App Service, the selected SQL tier and Azure OpenAI models, with sufficient quota and allocation capacity.
- Permission to register/configure a customer Microsoft Entra application if Microsoft member sign-in will be used. This is a separate guided step.
- An administrator username and strong password supplied securely during deployment.
- A decision on document trust: administrator approval without a scanner, or a separately configured and validated ClamAV scanner.
Customer installation steps
- Open the published Marketplace offer when it becomes available and choose the plan and subscription.
- Choose the managed resource group, region and portal name. Enter the portal administrator account; it is separate from your Microsoft account.
- Select the SQL tier and available text/voice model versions. Disable voice if it is not needed or unavailable. Confirm quota and regional checks.
- Choose the document trust policy. The template does not provision a scanner when an existing scanner is selected.
- Deploy and wait for resource creation, application installation and App Service warmup. Open the administrator URL and sign in.
- Open Customer setup at /admin/setup, verify the connections, then configure branding, knowledge and workspaces.
How the application is delivered
The publisher uploads one deployment ZIP containing the ARM template, deployment wizard, compiled Linux application ZIP and release manifest. Azure Applications stages these artifacts temporarily during installation. Native ARM OneDeploy copies the application into persistent customer App Service package storage.
The app runs with WEBSITE_RUN_FROM_PACKAGE=1. Ordinary stop/start and restart use the installed copy rather than a permanent publisher-controlled download host. Customer SQL data and private document originals live outside the application package. Reconstructing resources or repeating a full deployment needs fresh accessible installation artifacts.
SQL initializes automatically through the app’s managed identity on a dedicated portal SQL server. No separate SQL setup service, customer SQL security group or installation command is required. Keep that server dedicated to this app. Customer resources use normal Azure RBAC without a publisher deny lock.
Configure Microsoft member sign-in
- Create a single-tenant registration in the customer directory and configure the app’s HTTPS callback /.auth/login/aad/callback.
- Configure App Service Authentication using that registration and allow anonymous requests so the public site remains available. Keep its secret in secure Azure settings/Key Vault.
- Set the portal authentication provider and the customer tenant/registration IDs as described by Customer setup. Do not manually fake App Service authentication headers or platform indicators.
- Under People & access, grant each member access with their object ID in the customer directory and assigned workspace. Guest users need their guest object ID in that directory.
- Test with a member account and the separate portal administrator account. Confirm private pages require sign-in and unassigned users cannot access a workspace.
Verify the installation
- Publish a harmless test knowledge article and a saved branding draft.
- Submit, extract, review and download a harmless test document in an assigned workspace. Confirm anonymous access is denied.
- Test source-linked answers and each enabled voice feature. Validate scanning failures/recovery if a scanner is configured.
- Sign out and confirm return to the public root page while other Microsoft 365 sessions remain signed in.
- Arrange customer data retention, recovery and maintenance before using real records. Publishing a new offer package does not automatically upgrade existing installations.
Publisher packaging reference
Publishers maintaining the project build the Linux application first, then the bundled deployment ZIP. These are Bash build commands for the source project; customers do not need to build the application. The application ZIP does not require a permanent public download host.
- Use Node.js 24, npm and Docker with Linux containers.
- Preserve the tested application ZIP, release manifest, exact deployment ZIP and validation records before future builds.
- Upload the deployment ZIP to Partner Center only after completing the required template, staging and offer qualification. Do not upload the standalone application ZIP as the technical package.
bash scripts/build-application-zip.sh
bash scripts/build-deployment-zip.sh