diff --git a/app/backend/requirements.txt b/app/backend/requirements.txt
index f489c571cd..592463cf50 100644
--- a/app/backend/requirements.txt
+++ b/app/backend/requirements.txt
@@ -197,7 +197,7 @@ msal==1.30.0
     #   msal-extensions
 msal-extensions==1.2.0
     # via azure-identity
-msgraph-core==1.1.8
+msgraph-core==1.1.7
     # via msgraph-sdk
 msgraph-sdk==1.16.0
     # via -r requirements.in
diff --git a/docs/azd.md b/docs/azd.md
index 0ffb37a294..8cf8307814 100644
--- a/docs/azd.md
+++ b/docs/azd.md
@@ -17,7 +17,7 @@ The `azd up` command uses the `azure.yaml` file combined with the infrastructure
 
 Next, it provisions the resources based on `main.bicep` and `main.parameters.json`. At that point, since there is no default value for the OpenAI resource location, it asks you to pick a location from a short list of available regions. Then it will send requests to Azure to provision all the required resources. With everything provisioned, it runs the `postprovision` hook to process the local data and add it to an Azure AI Search index.
 
-Finally, it looks at `azure.yaml` to determine the Azure host (appservice, in this case) and uploads the zip to Azure App Service. The `azd up` command is now complete, but it may take another 5-10 minutes for the App Service app to be fully available and working, especially for the initial deploy.
+Finally, it looks at `azure.yaml` to determine the Azure host and uploads the zip to Azure App Service. The `azd up` command is now complete, but it may take another 5-10 minutes for the App Service app to be fully available and working, especially for the initial deploy.
 
 Related commands are `azd provision` for just provisioning (if infra files change) and `azd deploy` for just deploying updated app code.