Update DeploymentGuide.md

gpickett · web-flow · commit 2dc4d2853897 · 2025-04-28T18:05:38.000-07:00
diff --git a/documentation/DeploymentGuide.md b/documentation/DeploymentGuide.md
@@ -187,142 +187,6 @@ There are several ways to deploy the solution. You can deploy to run in Azure in
 
 When Deployment is complete, follow steps in [Set Up Authentication in Azure App Service](../documentation/azure_app_service_auth_setup.md) to add app authentication to your web app running on Azure App Service
 
-## Local Deployment
-To run the solution site and API backend only locally for development and debugging purposes, See the [local setup](#local-setup).
-
-## Manual Azure Deployment
-Manual Deployment differs from the 'Quick Deploy' option in that it will install an Azure Container Registry (ACR) service, and relies on the installer to build and push the necessary containers to this ACR.  This allows you to build and push your own code changes and provides a sample solution you can customize based on your requirements.
-
-### Prerequisites
-
-- Current Azure CLI installed
-  You can update to the latest version using ```az upgrade```
-- Azure account with appropriate permissions
-- Docker installed
-
-### Deploy the Azure Services
-All of the necessary Azure services can be deployed using the /deploy/macae.bicep script.  This script will require the following parameters:
-
-```
-az login
-az account set --subscription <SUBSCRIPTION_ID>
-az group create --name <RG_NAME> --location <RG_LOCATION>
-```
-To deploy the script you can use the Azure CLI.
-```
-az deployment group create \
-  --resource-group <RG_NAME> \
-  --template-file <BICEP_FILE> \
-  --name <DEPLOYMENT_NAME>
-```
-
-Note: if you are using windows with PowerShell, the continuation character (currently '\') should change to the tick mark ('').
-
-The template will require you fill in locations for Cosmos and OpenAI services.  This is to avoid the possibility of regional quota errors for either of these resources.
-
-### Create the Containers
-#### Get admin credentials from ACR
-
-Retrieve the admin credentials for your Azure Container Registry (ACR):
-
-```sh
-az acr credential show \
---name <e.g. macaeacr2t62qyozi76bs> \
---resource-group <rg-name>
-```
-
-#### Login to ACR
-
-Login to your Azure Container Registry:
-
-```sh
-az acr login --name <e.g. macaeacr2t62qyozi76bs>
-```
-
-#### Build and push the image
-
-Build the frontend and backend Docker images and push them  to your Azure Container Registry. Run the following from the src/backend and the src/frontend directory contexts:
-
-```sh
-az acr build \
---registry <e.g. macaeacr2t62qyozi76bs> \
---resource-group <rg-name> \
---image <e.g. backendmacae:latest> .
-```
-
-### Add images to the Container APP and Web App services
-
-To add your newly created backend image: 
-- Navigate to the Container App Service in the Azure portal
-- Click on Application/Containers in the left pane
-- Click on the "Edit and deploy" button in the upper left of the containers pane
-- In the "Create and deploy new revision" page, click on your container image 'backend'.  This will give you the option of reconfiguring the container image, and also has an Environment variables tab
-- Change the properties page to 
-  - point to your Azure Container registry with a private image type and your image name (e.g. backendmacae:latest)
-  - under "Authentication type" select "Managed Identity" and choose the 'mace-containerapp-pull'... identity setup in the bicep template
-- In the environment variables section add the following (each with a 'Manual entry' source):
-
-        name: 'COSMOSDB_ENDPOINT'
-        value: \<Cosmos endpoint>
-
-        name: 'COSMOSDB_DATABASE'
-        value: 'autogen'
-	    Note: To change the default, you will need to create the database in Cosmos
-			  
-        name: 'COSMOSDB_CONTAINER'
-        value: 'memory'
-
-        name: 'AZURE_OPENAI_ENDPOINT'
-        value: <Azure OpenAI endpoint>
-
-        name: 'AZURE_OPENAI_DEPLOYMENT_NAME'
-        value: 'gpt-4o'
-
-        name: 'AZURE_OPENAI_API_VERSION'
-        value: '2024-08-01-preview'
-		Note: Version should be updated based on latest available
-
-        name: 'FRONTEND_SITE_NAME'
-        value: 'https://<website Name>.azurewebsites.net'
-
-        name: 'APPLICATIONINSIGHTS_CONNECTION_STRING'
-        value: <Application Insights Connection String>
-
-- Click 'Save' and deploy your new revision
-
-To add the new container to your website run the following:
-
-```
-az webapp config container set --resource-group <resource_group_name> \
---name <container_name> \
---container-image-name <e.g. macaeacr2t62qyozi76bs.azurecr.io/frontendmacae:latest>  \
---container-registry-url <e.g. https://macaeacr2t62qyozi76bs.azurecr.io>
-```
-
-
-### Add the Entra identity provider to the Azure Web App
-To add the identity provider, please follow the steps outlined in [Set Up Authentication in Azure App Service](../documentation/azure_app_service_auth_setup.md)
-
-### Run locally and debug
-
-To debug the solution, you can use the Cosmos and OpenAI services you have manually deployed.  To do this, you need to ensure that your Azure identity has the required permissions on the Cosmos and OpenAI services. 
-
-- For OpenAI service, you can add yourself to the 'Cognitive Services OpenAI User' permission in the Access Control (IAM) pane of the Azure portal.  
-- Cosmos is a little more difficult as it requires permissions be added through script.  See these examples for more information: 
-  - [Use data plane role-based access control - Azure Cosmos DB for NoSQL | Microsoft Learn](https://learn.microsoft.com/en-us/azure/cosmos-db/nosql/security/how-to-grant-data-plane-role-based-access?tabs=built-in-definition%2Cpython&pivots=azure-interface-cli) 
-  - [az cosmosdb sql role assignment | Microsoft Learn](https://learn.microsoft.com/en-us/cli/azure/cosmosdb/sql/role/assignment?view=azure-cli-latest#az-cosmosdb-sql-role-assignment-create) 
-
-Add the appropriate endpoints from Cosmos and OpenAI services to your .env file.  
-Note that you can configure the name of the Cosmos database in the configuration.  This can be helpful if you wish to separate the data messages generated in local debugging from those associated with the cloud based solution.  If you choose to use a different database, you will need to create that database in the Cosmos instance as this is not done automatically.
-
-If you are using VSCode, you can use the debug configuration shown in the [local setup](#local-setup).
-
-## Requirements:
-
-- Python 3.10 or higher + PIP
-- Azure CLI, and an Azure Subscription
-- Visual Studio Code IDE
-
 # Local setup
 
 > **Note for macOS Developers**: If you are using macOS on Apple Silicon (ARM64) the DevContainer will **not** work. This is due to a limitation with the Azure Functions Core Tools (see [here](https://github.com/Azure/azure-functions-core-tools/issues/3112)).
