diff --git a/README.md b/README.md index eb583132..7bb9a38d 100644 --- a/README.md +++ b/README.md @@ -84,6 +84,8 @@ Follow the quick deploy steps on the deployment guide to deploy this solution > ⚠️ **Important: Check Azure OpenAI Quota Availability**
To ensure sufficient quota is available in your subscription, please follow [quota check instructions guide](./docs/quota_check.md) before you deploy the solution. +> πŸ› οΈ **Need Help?** Check our [Troubleshooting Guide](./docs/TroubleShootingSteps.md) for solutions to common deployment issues. +
### Prerequisites and costs @@ -118,6 +120,8 @@ Use the [Azure pricing calculator](https://azure.microsoft.com/en-us/pricing/cal >⚠️ **Important:** To avoid unnecessary costs, remember to take down your app if it's no longer in use, either by deleting the resource group in the Portal or running `azd down`. +For detailed cost estimation and pricing information, see the [Deployment Guide](./docs/DeploymentGuide.md). +

Business scenario diff --git a/docs/DeploymentGuide.md b/docs/DeploymentGuide.md index c57f2f0b..c7091278 100644 --- a/docs/DeploymentGuide.md +++ b/docs/DeploymentGuide.md @@ -1,8 +1,41 @@ # Deployment Guide +## **πŸš€ Quick Start** + +Get your Content Processing Solution up and running in Azure with this streamlined process: + +1. **πŸ” Verify Access** - Confirm you have the right Azure permissions and quota +2. **πŸ—οΈ Set Up Environment** - Create a fresh deployment environment +3. **πŸš€ Deploy to Azure** - Let Azure Developer CLI handle the infrastructure provisioning +4. **βœ… Configure & Validate** - Complete setup and verify everything works + +> **πŸ› οΈ Having Issues?** Our [Troubleshooting Guide](./TroubleShootingSteps.md) has solutions for common deployment problems. + +--- + ## **Pre-requisites** -To deploy this solution accelerator, ensure you have access to an [Azure subscription](https://azure.microsoft.com/free/) with the necessary permissions to create **resource groups, resources, app registrations, and assign roles at the resource group level**. This should include Contributor role at the subscription level and Role Based Access Control role on the subscription and/or resource group level. Follow the steps in [Azure Account Set Up](./AzureAccountSetup.md). +### Required Permissions & Access + +To deploy this solution accelerator, you need **Azure subscription access** with the following permissions: + +**βœ… Recommended Permissions:** +- **Owner** role at the subscription or resource group level +- **User Access Administrator** role at the subscription or resource group level + +> **Note:** These elevated permissions are required because the deployment creates Managed Identities and assigns roles to them automatically. + +**⚠️ Alternative Least-Privilege Setup:** +If you cannot use Owner + User Access Administrator roles, you'll need the following minimum permissions: + +| Permission | Required For | Scope | +|------------|-------------|-------| +| **Contributor** | Creating and managing Azure resources | Subscription or Resource Group | +| **User Access Administrator** | Assigning roles to Managed Identities | Resource Group | +| **Application Administrator** (Azure AD) | Creating app registrations for authentication | Tenant | +| **Role Based Access Control Administrator** | Managing role assignments | Resource Group | + +> **Important:** With least-privilege setup, you may need to perform some manual steps during deployment. Follow the steps in [Azure Account Set Up](./AzureAccountSetup.md) for detailed guidance. Check the [Azure Products by Region](https://azure.microsoft.com/en-us/explore/global-infrastructure/products-by-region/?products=all®ions=all) page and select a **region** where the following services are available: @@ -28,24 +61,43 @@ Set-ExecutionPolicy -Scope Process -ExecutionPolicy Bypass This will allow the scripts to run for the current session without permanently changing your system's policy. -
- ### **Important: Check Azure OpenAI Quota Availability** ⚠️ To ensure sufficient quota is available in your subscription, please follow [quota check instructions guide](./quota_check.md) before you deploy the solution. -
+### πŸ› οΈ Troubleshooting & Common Issues + +**Before starting deployment**, be aware of these common issues and solutions: + +| **Common Issue** | **Quick Solution** | **Full Guide Link** | +|-----------------|-------------------|---------------------| +| **ReadOnlyDisabledSubscription** | Check if you have an active subscription | [Troubleshooting Guide](./TroubleShootingSteps.md#readonlydisabledsubscription) | +| **InsufficientQuota** | Verify quota availability | [Quota Check Guide](./quota_check.md) | +| **ResourceGroupNotFound** | Create new environment with `azd env new` | [Troubleshooting Guide](./TroubleShootingSteps.md#resourcegroupnotfound) | +| **InvalidParameter (Workspace Name)** | Use compliant names (3-33 chars, alphanumeric) | [Troubleshooting Guide](./TroubleShootingSteps.md#workspace-name---invalidparameter) | +| **ResourceNameInvalid** | Follow Azure naming conventions | [Troubleshooting Guide](./TroubleShootingSteps.md#resourcenameinvalid) | +> **If you encounter deployment errors:** Refer to the [complete troubleshooting guide](./TroubleShootingSteps.md) with comprehensive error solutions. -## Deployment Options & Steps -Pick from the options below to see step-by-step instructions for GitHub Codespaces, VS Code Dev Containers, and Local Environments. +## Choose Your Deployment Environment -| [![Open in GitHub Codespaces](https://github.com/codespaces/badge.svg)](https://codespaces.new/microsoft/content-processing-solution-accelerator) | [![Open in Dev Containers](https://img.shields.io/static/v1?style=for-the-badge&label=Dev%20Containers&message=Open&color=blue&logo=visualstudiocode)](https://vscode.dev/redirect?url=vscode://ms-vscode-remote.remote-containers/cloneInVolume?url=https://github.com/microsoft/content-processing-solution-accelerator) | -|---|---| +Select one of the following options to deploy the Accelerator: + +### Environment Comparison + +| **Option** | **Best For** | **Prerequisites** | **Setup Time** | +|------------|--------------|-------------------|----------------| +| **GitHub Codespaces** | Quick deployment, no local setup required | GitHub account with Codespace enabled | ~3-5 minutes | +| **VS Code Dev Containers** | Fast deployment with local tools | Docker Desktop, VS Code | ~5-10 minutes | +| **Local Environment** | Enterprise environments, full control | All tools individually | ~15-30 minutes | + +**πŸ’‘ Recommendation:** For fastest deployment, start with **GitHub Codespaces** - no local installation required. + +---
- Deploy in GitHub Codespaces + Option 1: Deploy in GitHub Codespaces ### GitHub Codespaces @@ -62,7 +114,7 @@ You can run this solution using [GitHub Codespaces](https://docs.github.com/en/c
- Deploy in VS Code Dev Containers + Option 2: Deploy in VS Code Dev Containers ### VS Code Dev Containers @@ -79,7 +131,7 @@ You can run this solution in [VS Code Dev Containers](https://code.visualstudio.
- Deploy in your local Environment + Option 3: Deploy in your local Environment ### Local Environment @@ -103,7 +155,60 @@ If you're not using one of the above options for opening the project, then you'l
-
+### Choose Deployment Type (Optional) + +| **Aspect** | **Development/Testing (Default)** | **Production** | +|------------|-----------------------------------|----------------| +| **Configuration File** | `main.parameters.json` (sandbox) | Copy `main.waf.parameters.json` to `main.parameters.json` | +| **Security Controls** | Minimal (for rapid iteration) | Enhanced (production best practices) | +| **Cost** | Lower costs | Cost optimized | +| **Use Case** | POCs, development, testing | Production workloads | +| **Framework** | Basic configuration | [Well-Architected Framework](https://learn.microsoft.com/en-us/azure/well-architected/) | +| **Features** | Core functionality | Reliability, security, operational excellence | + +**To use production configuration:** + +Copy the contents from the production configuration file to your main parameters file: + +
+Option 1: Manual Copy (Recommended for beginners) + +1. Navigate to the `infra` folder in your project +2. Open `main.waf.parameters.json` in a text editor (like Notepad, VS Code, etc.) +3. Select all content (Ctrl+A) and copy it (Ctrl+C) +4. Open `main.parameters.json` in the same text editor +5. Select all existing content (Ctrl+A) and paste the copied content (Ctrl+V) +6. Save the file (Ctrl+S) + +
+ +
+Option 2: Using Command Line + +**For Linux/macOS/Git Bash:** +```bash +# Copy contents from production file to main parameters file +cat infra/main.waf.parameters.json > infra/main.parameters.json +``` + +**For Windows PowerShell:** +```powershell +# Copy contents from production file to main parameters file +Get-Content infra/main.waf.parameters.json | Set-Content infra/main.parameters.json +``` + +
+ +### Set VM Credentials (Optional - Production Deployment Only) + +> **Note:** This section only applies if you selected **Production** deployment type in section 3.1. VMs are not deployed in the default Development/Testing configuration. + +By default, random GUIDs are generated for VM credentials. To set custom credentials: + +```shell +azd env set AZURE_ENV_VM_ADMIN_USERNAME +azd env set AZURE_ENV_VM_ADMIN_PASSWORD +``` Consider the following settings during your deployment to modify specific settings: @@ -146,6 +251,40 @@ To adjust quota settings, follow these [steps](./AzureGPTQuotaSettings.md). Once you've opened the project in [Codespaces](#github-codespaces), [Dev Containers](#vs-code-dev-containers), or [locally](#local-environment), you can deploy it to Azure by following these steps: +#### Important: Environment Management for Redeployments + +> **⚠️ Critical:** If you're redeploying or have deployed this solution before, you **must** create a fresh environment to avoid conflicts and deployment failures. + +**Choose one of the following before deployment:** + +**Option A: Create a completely new environment (Recommended)** +```shell +azd env new +``` + +**Option B: Reinitialize in a new directory** +```shell +# Navigate to a new directory +cd ../my-new-deployment +azd init -t microsoft/content-processing-solution-accelerator +``` + +> **πŸ’‘ Why is this needed?** Azure resources maintain state information tied to your environment. Reusing an old environment can cause naming conflicts, permission issues, and deployment failures. + +#### Environment Naming Requirements + +When creating your environment name, follow these rules: +- **Maximum 14 characters** (will be expanded to meet Azure resource naming requirements) +- **Only lowercase letters and numbers** (a-z, 0-9) +- **No special characters** (-, _, spaces, etc.) +- **Examples:** `cpsapp01`, `mycontentapp`, `devtest123` + +> **πŸ’‘ Tip:** Use a descriptive prefix + environment + suffix to form a a unique string + +#### Deployment Steps + +> If you encounter any issues during the deployment process, refer to the [troubleshooting guide](../docs/TroubleShootingSteps.md) for detailed steps and solutions. + 1. Login to Azure: ```shell @@ -161,7 +300,7 @@ Once you've opened the project in [Codespaces](#github-codespaces), [Dev Contain > **Note:** To retrieve the Tenant ID required for local deployment, you can go to **Tenant Properties** in [Azure Portal](https://portal.azure.com/) from the resource list. Alternatively, follow these steps: > > 1. Open the [Azure Portal](https://portal.azure.com/). - > 2. Navigate to **Azure Active Directory** from the left-hand menu. + > 2. Navigate to **Microsoft Entra ID** from the left-hand menu. > 3. Under the **Overview** section, locate the **Tenant ID** field. Copy the value displayed. 2. Provision and deploy all the resources: @@ -171,7 +310,7 @@ Once you've opened the project in [Codespaces](#github-codespaces), [Dev Contain ``` > **Note:** This solution accelerator requires **Azure Developer CLI (azd) version 1.18.0 or higher**. Please ensure you have the latest version installed before proceeding with deployment. [Download azd here](https://learn.microsoft.com/en-us/azure/developer/azure-developer-cli/install-azd). -3. Provide an `azd` environment name (e.g., "cpsapp"). +3. **Provide an `azd` environment name** - Use the naming requirements above (e.g., "cpsapp01"). 4. Select a subscription from your Azure account and choose a location that has quota for all the resources. - This deployment will take *4-6 minutes* to provision the resources in your account and set up the solution with sample data. - If you encounter an error or timeout during deployment, changing the location may help, as there could be availability constraints for the resources. @@ -185,33 +324,10 @@ Once you've opened the project in [Codespaces](#github-codespaces), [Dev Contain > #### Important Note : Before accessing the application, ensure that all **[Post Deployment Steps](#post-deployment-steps)** are fully completed, as they are critical for the proper configuration of **Data Ingestion** and **Authentication** functionalities. -7. If you are done trying out the application, you can delete the resources by running `azd down`. - -### πŸ› οΈ Troubleshooting - If you encounter any issues during the deployment process, please refer [troubleshooting](../docs/TroubleShootingSteps.md) document for detailed steps and solutions +> If you encounter any issues during the deployment process, refer to the [troubleshooting guide](../docs/TroubleShootingSteps.md) for detailed steps and solutions. ## Post Deployment Steps -1. Optional: Publishing Local Build Container to Azure Container Registry - - If you need to rebuild the source code and push the updated container to the deployed Azure Container Registry, follow these steps: - - - **Linux/macOS**: - ```bash - cd ./infra/scripts/ - - ./docker-build.sh - ``` - - - **Windows (PowerShell)**: - ```powershell - cd .\infra\scripts\ - - .\docker-build.ps1 - ``` - - This will create a new Azure Container Registry, rebuild the source code, package it into a container, and push it to the Container Registry created. - -2. **Register Schema Files** +1. **Register Schema Files** > Want to customize the schemas for your own documents? [Learn more about adding your own schemas here.](./CustomizeSchemaData.md) @@ -282,35 +398,140 @@ Once you've opened the project in [Codespaces](#github-codespaces), [Dev Contain ./upload_files.ps1 https://<< API Service Endpoint >>/contentprocessor/submit .\propertyclaims <> ``` -3. **Add Authentication Provider** +2. **Add Authentication Provider** - Follow steps in [App Authentication](./ConfigureAppAuthentication.md) to configure authenitcation in app service. Note that Authentication changes can take up to 10 minutes. -4. **Deleting Resources After a Failed Deployment** +## Deployment Success Validation + +After deployment completes, use this checklist to verify everything is working correctly: + +### Deployment Validation Checklist + +**1. Basic Deployment Verification** +- [ ] `azd up` completed successfully without errors +- [ ] All Azure resources are created in the resource group +- [ ] Both Web and API container apps are running + +**2. Container Apps Health Check** +```powershell +# Test Web App (replace with actual URL from deployment output) +curl -I https:/// + +# Test API App (replace with actual URL) +curl -I https:///health +``` +**Expected Result:** Both should return HTTP 200 status + + +### Sample Test Commands + +**API Health Check:** +```bash +curl https:///health +``` + +**Web App Accessibility:** +```bash +curl -I https:/// +``` + +**Schema Registration Verification:** +```bash +curl https:///schemavault/schemas +``` - - Follow steps in [Delete Resource Group](./DeleteResourceGroup.md) if your deployment fails and/or you need to clean up the resources. - ## Running the application To help you get started, here's the [Sample Workflow](./SampleWorkflow.md) you can follow to try it out. -## Environment configuration for local development & debugging -**Creating env file** +## Clean Up Resources -> Navigate to the `src` folder of the project. +When you're done testing the solution or need to clean up after deployment issues, you have several options: -1. Locate the `.env` file inside the `src` directory. -2. To fill in the required values, follow these steps -- Go to the Azure Portal. -- Navigate to your **Resource Group**. -- Open the **Web Container** resource. -- In the left-hand menu, select **Containers**. -- Go to the **Environment Variables** tab. -- Copy the necessary environment variable values and paste them into your local `.env` file. - +### 🧹 Environment Cleanup + +**To clean up azd environments:** +```powershell +# List all environments +azd env list + +# Clean up a specific environment +azd env select +azd down --force --purge +``` + +> **Tip:** If you have old environments that failed deployment or are no longer needed, use the commands above to clean them up before creating new ones. + +### πŸ—‘οΈ Azure Resource Group Cleanup + +**To clean up Azure resource groups (if needed):** +```powershell +# List resource groups +az group list --output table + +# Delete a specific resource group +az group delete --name --yes --no-wait +``` + +### πŸ“ Deleting Resources After a Failed Deployment + +- Follow detailed steps in [Delete Resource Group](./DeleteResourceGroup.md) if your deployment fails and/or you need to clean up the resources. + +> **⚠️ Important:** Always ensure you want to permanently delete resources before running cleanup commands. These operations cannot be undone. + +### Troubleshooting Failed Validation + +**If any checks fail:** +1. Check Azure Portal β†’ Resource Group β†’ Container Apps for error logs +2. Review deployment logs: `azd show` +3. Verify all post-deployment steps are completed +4. Check [Troubleshooting Guide](./TroubleShootingSteps.md) for specific error solutions ## Next Steps -Now that you've completed your deployment, you can start using the solution. Try out these things to start getting familiar with the capabilities: -* Open the web container app URL in your browser and explore the web user interface and upload your own invoices. -* [Create your own schema definition](./CustomizeSchemaData.md), so you can upload and process your own types of documents. -* [Ingest the API](API.md) for processing documents programmatically. +Now that you've validated your deployment, you can start add your own schema or modify the existing one to meet your requirements: + +### Getting Started +* **Create Custom Schemas:** [Learn how to add your own document schemas](./CustomizeSchemaData.md) + +* **API Integration:** [Explore programmatic document processing](API.md) + +## Local Development + +If you need to modify the source code and test changes locally, follow these steps: + +### Publishing Local Build Container to Azure Container Registry + +To rebuild the source code and push the updated container to the deployed Azure Container Registry: + +- **Linux/macOS**: + ```bash + cd ./infra/scripts/ + + ./docker-build.sh + ``` + +- **Windows (PowerShell)**: + ```powershell + cd .\infra\scripts\ + + .\docker-build.ps1 + ``` + +This will rebuild the source code, package it into a container, and push it to the Azure Container Registry created during deployment. + +### Environment Configuration for Local Development & Debugging + +**Creating env file** + +> Navigate to the `src` folder of the project. + +1. Locate the `.env` file inside the `src` directory. +2. To fill in the required values, follow these steps: + - Go to the Azure Portal. + - Navigate to your **Resource Group**. + - Open the **Web Container** resource. + - In the left-hand menu, select **Containers**. + - Go to the **Environment Variables** tab. + - Copy the necessary environment variable values and paste them into your local `.env` file. + \ No newline at end of file diff --git a/docs/GoldenPathWorkflows.md b/docs/GoldenPathWorkflows.md new file mode 100644 index 00000000..ef78b4c2 --- /dev/null +++ b/docs/GoldenPathWorkflows.md @@ -0,0 +1,205 @@ +# Golden Path Workflows Guide + +This guide provides detailed step-by-step workflows for getting the most out of the Content Processing Solution Accelerator. These "golden path" workflows represent the most common and effective use cases for the solution. + +## Overview + +The golden path workflows are designed to: +- Demonstrate the full capabilities of the solution +- Provide a structured learning experience +- Showcase best practices for document processing +- Help users understand the confidence scoring and validation features + +## Workflow 1: Invoice Processing Golden Path + +### πŸ“‹ Prerequisites +- Solution deployed and validated successfully +- Sample schemas registered (Invoice schema) +- Authentication configured + +### πŸš€ Step-by-Step Process + +1. **Access the Web Interface** + - Navigate to your deployed web app URL + - Log in using your configured authentication + +2. **Select Invoice Schema** + - In the Processing Queue pane, select "Invoice" from the schema dropdown + - Verify the schema shows as available + +3. **Upload Sample Invoice** + - Click "Import Content" button + - Select an invoice file from the sample data (PDF, PNG, or JPEG) + - Click "Upload" to submit + +4. **Monitor Processing** + - Watch the file status change from "Uploaded" β†’ "Processing" β†’ "Completed" + - This typically takes 1-2 minutes + +5. **Review Extracted Data** + - Click on the completed file to open the review interface + - Examine the extracted data in the "Extracted Results" tab + - Compare with the source document in the "Source Document" pane + +6. **Validate and Modify Results** + - Edit any incorrect data in the JSON output + - Add notes in the "Comments" section + - Pay attention to confidence scores for each field + +7. **Save and Approve** + - Click "Save" to store your modifications + - Review the process steps in the "Process Steps" tab + +### 🎯 Expected Outcomes +- βœ… Invoice data accurately extracted (vendor, amounts, dates, line items) +- βœ… Confidence scores above 80% for most fields +- βœ… Any low-confidence fields flagged for manual review +- βœ… Process steps show successful extraction, mapping, and evaluation + +## Workflow 2: Property Claims Golden Path + +### πŸ“‹ Prerequisites +- Invoice workflow completed successfully +- Property Loss Damage Claim Form schema registered + +### πŸš€ Step-by-Step Process + +1. **Switch to Property Claims Schema** + - Select "Property Loss Damage Claim Form" from the schema dropdown + +2. **Upload Property Damage Document** + - Import a property claim form from the sample data + - Monitor the processing workflow + +3. **Validate Complex Extraction** + - Review extracted claim details, damages, and policy information + - Note how the system handles form fields vs. free text + +4. **Test Validation Features** + - Modify extracted data to test validation rules + - Add detailed comments about damage assessments + +5. **Process Multiple Documents** + - Upload additional property claim documents + - Compare extraction accuracy across different document formats + +### 🎯 Expected Outcomes +- βœ… Complex form data accurately extracted +- βœ… Multi-modal content (text, images, tables) processed correctly +- βœ… Validation rules applied appropriately + +## Workflow 3: Custom Document Processing Golden Path + +### πŸ“‹ Prerequisites +- Basic workflows completed +- Understanding of your specific document types + +### πŸš€ Step-by-Step Process + +1. **Create Custom Schema** + - Follow the [Custom Schema Guide](./CustomizeSchemaData.md) + - Define your document structure and required fields + +2. **Register Your Schema** + - Use the schema registration scripts + - Validate schema is available in the web interface + +3. **Test with Sample Documents** + - Start with 2-3 representative documents + - Process and review initial results + +4. **Refine Extraction Quality** + - Analyze confidence scores and accuracy + - Modify schema definitions if needed + - Re-test with updated schema + +5. **Scale to Production** + - Process larger document batches + - Establish quality thresholds + - Set up automated workflows using the API + +### 🎯 Expected Outcomes +- βœ… Custom schema accurately processes your document types +- βœ… Confidence scoring helps identify manual review needs +- βœ… Workflow scales to handle production volumes + +## Advanced Workflows + +### Multi-Schema Processing +- Process different document types in the same session +- Compare extraction approaches across schemas +- Understand when to use different processing strategies + +### API Integration Golden Path +- Use programmatic APIs for document submission +- Implement webhook callbacks for processing notifications +- Build custom validation and approval workflows + +### Batch Processing Workflow +- Upload multiple documents simultaneously +- Monitor batch processing status +- Export results for downstream systems + +## Best Practices + +### Quality Assurance +- Always review low-confidence extractions manually +- Use comments to document validation decisions +- Track accuracy improvements over time + +### Confidence Score Interpretation +- **90-100%**: High confidence, likely accurate +- **70-89%**: Medium confidence, review recommended +- **Below 70%**: Low confidence, manual review required + +### Performance Optimization +- Use consistent document formats when possible +- Ensure good image quality for scanned documents +- Batch similar document types for better consistency + +## Troubleshooting Common Issues + +### Low Extraction Accuracy +- Check document quality and formatting +- Verify schema matches document structure +- Review and update system prompts if needed + +### Processing Timeouts +- Reduce document file sizes +- Check Azure quota availability +- Monitor system logs for errors + +### Authentication Issues +- Verify app registration configuration +- Check user permissions and role assignments +- Review authentication provider settings + +## Next Steps + +After completing these golden path workflows: + +1. **Explore Advanced Features** + - Custom validation rules + - Webhook integrations + - Batch processing APIs + +2. **Integrate with Your Systems** + - Connect to downstream databases + - Set up automated workflows + - Implement custom business logic + +3. **Scale Your Solution** + - Monitor performance metrics + - Optimize for your specific use cases + - Plan for production deployment + +## Support and Resources + +- **Technical Documentation**: [API Guide](./API.md) +- **Troubleshooting**: [Common Issues](./TroubleShootingSteps.md) +- **Sample Data**: [Download samples](../src/ContentProcessorAPI/samples) +- **Community**: [Submit issues](https://github.com/microsoft/content-processing-solution-accelerator/issues) + +--- + +*This guide is based on the automated test suite golden path workflows that validate the core functionality of the solution.* \ No newline at end of file diff --git a/docs/images/add_auth_provider_api_1.png b/docs/images/add_auth_provider_api_1.png index 607e5dd9..dafb7b94 100644 Binary files a/docs/images/add_auth_provider_api_1.png and b/docs/images/add_auth_provider_api_1.png differ diff --git a/docs/images/add_auth_provider_web_1.png b/docs/images/add_auth_provider_web_1.png index 3d45240f..adccd86f 100644 Binary files a/docs/images/add_auth_provider_web_1.png and b/docs/images/add_auth_provider_web_1.png differ diff --git a/docs/images/configure_app_registration_api_1.png b/docs/images/configure_app_registration_api_1.png index 0df82d68..ce946970 100644 Binary files a/docs/images/configure_app_registration_api_1.png and b/docs/images/configure_app_registration_api_1.png differ diff --git a/docs/images/configure_app_registration_web_1.png b/docs/images/configure_app_registration_web_1.png index 93068836..ae503aae 100644 Binary files a/docs/images/configure_app_registration_web_1.png and b/docs/images/configure_app_registration_web_1.png differ