From 96004e26ba8b00007beae109b2541d8975d16d41 Mon Sep 17 00:00:00 2001 From: Takashi Takebayashi Date: Fri, 10 Oct 2025 08:55:13 +0900 Subject: [PATCH] Fix typo: programatically -> programmatically --- .../quickstarts/tpe/teams-phone-extensibility-quickstart.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/articles/communication-services/quickstarts/tpe/teams-phone-extensibility-quickstart.md b/articles/communication-services/quickstarts/tpe/teams-phone-extensibility-quickstart.md index acb35d5218e40..3a0b9d56d45e4 100644 --- a/articles/communication-services/quickstarts/tpe/teams-phone-extensibility-quickstart.md +++ b/articles/communication-services/quickstarts/tpe/teams-phone-extensibility-quickstart.md @@ -229,7 +229,7 @@ The following steps demonstrate how to receive and answer an incoming Teams call 1. Complete client and server consent as defined in [Access a user's Teams Phone separate from their Teams client](https://github.com/Azure/communication-preview/blob/master/Teams%20Phone%20Extensibility/teams-phone-extensibility-access-teams-phone.md). > [!NOTE] -> For the Azure Communication Services resource, ensure the data location matches the Teams Tenant location to comply with data boundary regulations. You can retrieve programatically details about tenant organisation via [Get organization](/graph/api/organization-get) +> For the Azure Communication Services resource, ensure the data location matches the Teams Tenant location to comply with data boundary regulations. You can retrieve programmatically details about tenant organisation via [Get organization](/graph/api/organization-get) > #### Setup and host your Azure dev tunnels