commit

Author: Tejasri-Microsoft

docs/ConfigureAppAuthentication.md

@@ -1,24 +1,10 @@
 # Set up Authentication in Azure Container App
 
-> ### ✅ Recommended: run the authentication script first
->
-> `azd up` no longer runs authentication setup automatically. Run the script below after deployment:
->
-> **Windows:**
-> ```powershell
-> ./infra/scripts/setup_auth.ps1
-> ```
->
-> **macOS/Linux:**
-> ```bash
-> bash ./infra/scripts/setup_auth.sh
-> ```
->
-> See [DeploymentGuide.md § 5.3](./DeploymentGuide.md#53-configure-authentication-manual-script) for step-by-step instructions.
->
-> Follow the portal/manual steps below if:
-> - Your tenant policy prohibits programmatic app registration or secret creation
-> - The script reports a permission or policy failure that cannot be resolved in your current identity
+This guide describes the portal/manual steps to configure authentication after deployment.
+
+Use this path when:
+- Your tenant policy prohibits programmatic app registration or secret creation
+- Script-based setup is not available in your current identity
 
 This document provides step-by-step instructions to configure Azure App Registrations for the front-end and back-end applications.
 

docs/DeploymentGuide.md

@@ -349,31 +349,15 @@ After schema registration completes, upload the sample bundles as a separate exp
 bash ./infra/scripts/upload_sample_data.sh
 ```
 
-### 5.3 Configure Authentication (Manual Script)
+### 5.3 Configure Authentication (Portal)
 
-Run authentication setup as an explicit step after post-deployment data setup:
+Configure authentication as an explicit step after post-deployment data setup by following:
 
-**Windows (PowerShell):**
-
-```powershell
-./infra/scripts/setup_auth.ps1
-```
-
-**macOS/Linux:**
-
-```bash
-bash ./infra/scripts/setup_auth.sh
-```
-
-The auth script is idempotent and performs preflight validation before making changes.
-
-#### Required Permissions for auth setup
+- [Set up Authentication in Azure Container App](./ConfigureAppAuthentication.md)
 
-- Create/update app registrations: **Application Administrator**, **Cloud Application Administrator**, or **Global Administrator**
-- Grant admin consent: **Cloud Application Administrator** or **Global Administrator**
-- Update Container Apps auth/secret settings: **Contributor** on the deployment resource group
+If your tenant policy blocks automatic app registration/secret creation in the portal flow, use:
 
-If permissions are insufficient, the script exits early (or warns before consent) with clear remediation guidance.
+- [Manual App Registration Configuration](./ManualAppRegistrationConfiguration.md)
 
 > **Note:** EasyAuth can take up to 10 minutes to fully propagate. If the Web app returns 500/401 immediately after setup, wait a few minutes and retry.