Skip to content

Commit e0c6e87

Browse files
authored
Revert upgrade of msgraph-core SDK (#2257)
* Configure Azure Developer Pipeline * Revert msgraph-core upgrade
1 parent 443841d commit e0c6e87

File tree

2 files changed

+2
-2
lines changed

2 files changed

+2
-2
lines changed

app/backend/requirements.txt

+1-1
Original file line numberDiff line numberDiff line change
@@ -197,7 +197,7 @@ msal==1.30.0
197197
# msal-extensions
198198
msal-extensions==1.2.0
199199
# via azure-identity
200-
msgraph-core==1.1.8
200+
msgraph-core==1.1.7
201201
# via msgraph-sdk
202202
msgraph-sdk==1.16.0
203203
# via -r requirements.in

docs/azd.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -17,7 +17,7 @@ The `azd up` command uses the `azure.yaml` file combined with the infrastructure
1717

1818
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.
1919

20-
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.
20+
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.
2121

2222
Related commands are `azd provision` for just provisioning (if infra files change) and `azd deploy` for just deploying updated app code.
2323

0 commit comments

Comments
 (0)