Post Deployment

Follow the instruction below to complete the setup of Microsoft Entra ID authentication for the Core API and Chat applications after the deployment is complete.

Update App Configuration settings

  1. Sign in to the Azure portal as at least a Contributor.

  2. Navigate to the resource group that was created as part of the deployment.

  3. Select the App Configuration resource and select Configuration explorer to view the values.

  4. Enter entra in the search box to filter the results.

  5. Check the box next to Key in the header to select all items.

  6. Select Edit to open a JSON editor for the selected items.

    The configuration settings are filtered by entra and all items are selected.

  7. Replace the values for the following settings with the values that you recorded earlier:

    • FoundationaLLM:Chat:Entra:ClientId: The Application (client) ID of the client application that you created earlier.
    • FoundationaLLM:Chat:Entra:Scopes: The fully-qualified scopes path for the API application that you created earlier. For example, it should look something like api://FoundationaLLM-Core/Data.Read.
    • FoundationaLLM:Chat:Entra:TenantId: The Directory (tenant) ID of the client application that you created earlier.
    • FoundationaLLM:CoreAPI:Entra:ClientId: The Application (client) ID of the API application that you created earlier.
    • FoundationaLLM:CoreAPI:Entra:TenantId: The Directory (tenant) ID of the API application that you created earlier.

  8. Validate the following values while reviewing the settings:

    • FoundationaLLM:Chat:Entra:CallbackPath: Should be /signin-oidc.
    • FoundationaLLM:Chat:Entra:Instance: Should be https://login.microsoftonline.com/.
    • FoundationaLLM:CoreAPI:Entra:CallbackPath: Should be /signin-oidc.
    • FoundationaLLM:CoreAPI:Entra:Instance: Should be https://login.microsoftonline.com/.
    • FoundationaLLM:CoreAPI:Entra:Scopes: Should be Data.Read.

  9. Select Apply to save the changes.

Next steps

Now that Entra authentication is fully configured, restart the Core API and chat applications to apply the changes. Navigate to your chat application or refresh the page if it is already open. It should automatically prompt you to sign in with your Microsoft Entra ID account.

Restart Core API and Chat UI applications in an ACA Deployment

To restart the Core API and Chat applications in an Azure Container Apps (ACA) deployment, you will need to navigate to the Core API and Chat applications and restart their container revisions, as indicated in the following Azure Portal screenshot:

Restarting the Core API Azure Container App.

  1. From the Revisions blade in the left navigation panel of the Core API or Chat UI container app detail page in Azure Portal, select the name of the running revision.
  2. A dialog panel titled Revision details should appear on the right side of the browser with a Restart button at the top. Select the Restart button to restart the running container.

Restarting in this manner will need to be performed for both the Core API container app and the Chat UI container app.

Restart Core API and Chat UI applications in an AKS Deployment

To restart the Core API and Chat applications in an Azure Kubernetes Service (AKS) deployment, you will need to navigate to the AKS detail page in Azure Portal and perform the following:

  1. Select the Workloads blade from the left navigation panel.
  2. Select the Pods tab from the Workloads detail page.
  3. Select the Core API and Chat UI pods from the list (it helps if you select default in the Filter by namespace dropdown first).
  4. Select the Delete button to terminate the currently running pods. New pods will be instantiated to take their place.

Restarting containers in AKS.

Edit this page