> For the complete documentation index, see [llms.txt](https://maqsoftware.gitbook.io/poevalidator-technical-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://maqsoftware.gitbook.io/poevalidator-technical-documentation/readme.md).

# POE Validator Technical Documentation

POE Validator is deployed through Azure Marketplace as a managed application. This documentation set walks through required Azure subscription preparation, Microsoft Entra app registration, marketplace deployment, post-deployment redirect URI setup, and first-time administrator bootstrap using mock mode.

## What POE Validator Deploys

POE Validator provisions the application runtime and supporting Azure services needed for deployment and operations.

* Azure App Service for the web application
* Azure App Service Plan for web hosting capacity
* Azure OpenAI for model deployment and inference
* Azure Storage for application data and assets
* Azure Cosmos DB for metadata persistence
* Azure Log Analytics for operational logging
* Azure Application Insights for monitoring and diagnostics
* Managed identity and related Azure access configuration

## Recommended Reading Order

Use the documents in this order for a first-time deployment.

| Step | Document                                                                                                       | Purpose                                                                           |
| ---- | -------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------- |
| 1    | [Prerequisite/prerequisite](/poevalidator-technical-documentation/1.-prerequisite/prerequisite.md)             | Confirm required tools, access, and baseline readiness                            |
| 2    | [Pre-Deployment/App Registration](/poevalidator-technical-documentation/2.-pre-deployment/app-registration.md) | Complete application registration and pre-deployment identity setup               |
| 3    | [Deploy/deploy](/poevalidator-technical-documentation/3.-deploy/deploy.md)                                     | Follow the Azure Marketplace deployment flow and capture managed resource details |
| 4    | [Configure/configure](/poevalidator-technical-documentation/4.-configure/configure.md)                         | Add the deployed App Service URL as the redirect URI in app registration          |
| 5    | [MockUser/Mock User](/poevalidator-technical-documentation/5.-mockuser/mock-user.md)                           | Bootstrap first admin access and disable mock mode after setup                    |

## Deployment Workflow Summary

1. Register required Azure resource providers in the target subscription.
2. Create a single-tenant Microsoft Entra app registration for POE Validator.
3. Save the application display name, client ID, and tenant ID.
4. Deploy POE Validator from Azure Marketplace using the saved identity values and deployment inputs.
5. After deployment, copy the App Service URL and add it as a redirect URI in app registration.
6. Sign in using mock mode, assign a real SuperAdmin, and then disable mock mode.

## Important Deployment Inputs

Prepare these values before you start deployment:

* Azure subscription and resource group
* Primary Azure region
* Environment name (Development, Testing, Staging, or Production)
* App naming values
* Microsoft Entra tenant ID
* Microsoft Entra client ID
* GPT model and model version
* Mock email address
* App Service Plan SKU and Storage SKU
* OpenAI capacity and log retention values

## Document Notes

* [Prerequisite/prerequisite](/poevalidator-technical-documentation/1.-prerequisite/prerequisite.md) Lists the required Azure access, tools, permissions, and environment prerequisites that must be completed before deployment.
* [Pre-Deployment/App Registration](/poevalidator-technical-documentation/2.-pre-deployment/app-registration.md) Guides you through creating and configuring the Microsoft Entra app registration required for authentication
* [Deploy/deploy](/poevalidator-technical-documentation/3.-deploy/deploy.md) should be treated as the primary deployment guide in this repository.
* [Configure/configure](/poevalidator-technical-documentation/4.-configure/configure.md) is a post-deployment step and depends on the deployed App Service URL.
* [MockUser/Mock User](/poevalidator-technical-documentation/5.-mockuser/mock-user.md) should be used only for first-time bootstrap and should be disabled after real admin access is configured.

## Intended Audience

* Azure administrators deploying the managed application
* Microsoft Entra administrators creating app registration and granting consent
* Application administrators configuring initial access control
* Operators validating deployment and readiness post rollout

## Outcome Of This Guide

After completing the full sequence, teams should have:

* A deployed POE Validator managed application in Azure
* A working Microsoft Entra sign-in flow with correct redirect URI configuration
* Initial admin access configured through real users or groups
* Mock mode disabled and the environment ready for normal use

***

*Last updated: August 2026*

*© MAQ Software — POE Validator Technical Documentation*