feat: rebrand ttk

samples/nodejs-typescript-food-catalog/.funcignore

@@ -11,6 +11,6 @@ scripts
 *.js.map
 local.settings.json
 readme.md
-teamsapp.local.yml
-teamsapp.yml
+m365agents.local.yml
+m365agents.yml
 tsconfig.json

samples/nodejs-typescript-food-catalog/.gitignore

@@ -48,6 +48,6 @@ __queuestorage__
 __azurite_db*__.json
 _storage_emulator
 
-# Teams Toolkit
+# Microsoft 365 Agents Toolkit
 build
 appPackage/build

samples/nodejs-typescript-food-catalog/.tours/ttk.tour

@@ -14,7 +14,7 @@
       },
       {
         "file": "appPackage/manifest.json",
-        "description": "The `graphConnector.notificationUrl` represents the endpoint which will receive a request when an admin either enables or disables a connection in the Teams admin center. As your endpoint is running locally during development, you'll need a Dev tunnel to open your localhost to the internet.\r\n\r\nNext, let's take a look at how Teams Toolkit handles all of this when you press `F5`.",
+        "description": "The `graphConnector.notificationUrl` represents the endpoint which will receive a request when an admin either enables or disables a connection in the Teams admin center. As your endpoint is running locally during development, you'll need a Dev tunnel to open your localhost to the internet.\r\n\r\nNext, let's take a look at how Microsoft 365 Agents Toolkit handles all of this when you press `F5`.",
         "line": 33
       },
       {
@@ -54,26 +54,26 @@
       },
       {
         "file": ".vscode/tasks.json",
-        "description": "This task executes the `Provision` stage in the `teamsapp.local.yml` file.",
+        "description": "This task executes the `Provision` stage in the `m365agents.local.yml` file.",
         "line": 117
       },
       {
-        "file": "teamsapp.local.yml",
-        "description": "This is a project file which is used to automate Microsoft 365 development tasks using Teams Toolkit.",
+        "file": "m365agents.local.yml",
+        "description": "This is a project file which is used to automate Microsoft 365 development tasks using Microsoft 365 Agents Toolkit.",
         "line": 1
       },
       {
-        "file": "teamsapp.local.yml",
+        "file": "m365agents.local.yml",
         "description": "This action executes a script that ensures the Azurite tables are populated with data so that we have content to ingest into Microsoft 365.",
         "line": 10
       },
       {
-        "file": "teamsapp.local.yml",
+        "file": "m365agents.local.yml",
         "description": "This action executes a script to increment the app manifest version each time we start a debug session, this ensures that we don't get conflicts when the app package is uploaded to Teams admin center.",
         "line": 16
       },
       {
-        "file": "teamsapp.local.yml",
+        "file": "m365agents.local.yml",
         "description": "This action creates the Microsoft Entra app registration and writes values to the `env\\.env.local` and `env\\.env.local.user` files.",
         "line": 22
       },
@@ -94,11 +94,11 @@
       },
       {
         "file": "env/.env.local.user",
-        "description": "This file represents the environment variables for the local environment. It is specifically designed for storing secured credentials which are encrypted by Teams Toolkit.",
+        "description": "This file represents the environment variables for the local environment. It is specifically designed for storing secured credentials which are encrypted by Microsoft 365 Agents Toolkit.",
         "line": 1
       },
       {
-        "file": "teamsapp.local.yml",
+        "file": "m365agents.local.yml",
         "description": "This action update the app registration with the information from the manifest to apply the API permission scopes and configure the `Application ID URI`.",
         "line": 35
       },
@@ -118,7 +118,7 @@
         "line": 22
       },
       {
-        "file": "teamsapp.local.yml",
+        "file": "m365agents.local.yml",
         "description": "This action creates the app package, which contains the app manifest file and icons.",
         "line": 44
       },
@@ -128,12 +128,12 @@
         "line": 1
       },
       {
-        "file": "teamsapp.local.yml",
+        "file": "m365agents.local.yml",
         "description": "This action writes values from the environment files to the `local.settings.json` file which enables the Azure Function to read these values at runtime.",
         "line": 54
       },
       {
-        "file": "teamsapp.local.yml",
+        "file": "m365agents.local.yml",
         "description": "This task uploads the app package to the Teams admin center.\r\n\r\nYou'll need to navigate to the [Teams admin center](https://aka.ms/tac) and publish the app.",
         "line": 68
       },

samples/nodejs-typescript-food-catalog/assets/sample.json

@@ -2,20 +2,20 @@
   {
     "name": "pnp-graph-connector-nodejs-typescript-food-catalog",
     "source": "pnp",
-    "title": "Ingest custom API data using TypeScript, Node.js and Teams Toolkit for Visual Studio Code",
-    "shortDescription": "This sample project uses Teams Toolkit to simplify the process of creating a Microsoft Graph connector that ingests data from a custom API to Microsoft Graph",
+    "title": "Ingest custom API data using TypeScript, Node.js and Microsoft 365 Agents Toolkit for Visual Studio Code",
+    "shortDescription": "This sample project uses Microsoft 365 Agents Toolkit to simplify the process of creating a Microsoft Graph connector that ingests data from a custom API to Microsoft Graph",
     "url": "https://github.com/pnp/graph-connectors-samples/tree/main/samples/nodejs-typescript-food-catalog",
     "downloadUrl": "https://pnp.github.io/download-partial/?url=https://github.com/pnp/graph-connectors-samples/tree/main/samples/nodejs-typescript-food-catalog",
     "longDescription": [
-      "This sample project uses Teams Toolkit for Visual Studio Code to simplify the process of creating a Microsoft Graph connector that ingests data from a custom API to Microsoft Graph. It provides an end to end example of creating the connector, ingesting content and refreshing the ingested content on a schedule. It also includes the simplified admin experience which means that admins can toggle the connector on and off from the Microsoft Teams admin center."
+      "This sample project uses Microsoft 365 Agents Toolkit for Visual Studio Code to simplify the process of creating a Microsoft Graph connector that ingests data from a custom API to Microsoft Graph. It provides an end to end example of creating the connector, ingesting content and refreshing the ingested content on a schedule. It also includes the simplified admin experience which means that admins can toggle the connector on and off from the Microsoft Teams admin center."
     ],
     "creationDateTime": "2023-11-02",
     "updateDateTime": "2025-02-21",
     "products": [
       "Microsoft Graph connectors",
       "Microsoft Graph",
       "Microsoft 365 Copilot",
-      "TeamsToolkit"
+      "Microsoft 365 Agents Toolkit"
     ],
     "metadata": [
       {
@@ -83,8 +83,8 @@
         "url": "https://blog.mastykarz.nl/easily-debug-microsoft-graph-javascript-sdk-requests/"
       },
       {
-        "name": "Teams Toolkit for Visual Studio Code",
-        "description": "Learn more about the Teams Toolkit for Visual Studio Code.",
+        "name": "Microsoft 365 Agents Toolkit for Visual Studio Code",
+        "description": "Learn more about the Microsoft 365 Agents Toolkit for Visual Studio Code.",
         "url": "https://learn.microsoft.com/microsoftteams/platform/toolkit/teams-toolkit-fundamentals?pivots=visual-studio-code-v5"
       }
     ]

samples/nodejs-typescript-food-catalog/readme.md

@@ -1,8 +1,8 @@
-# Ingest custom API data using TypeScript, Node.js and Teams Toolkit for Visual Studio Code
+# Ingest custom API data using TypeScript, Node.js and Microsoft 365 Agents Toolkit for Visual Studio Code
 
 ## Summary
 
-This sample project uses Teams Toolkit for Visual Studio Code to simplify the process of creating a [Microsoft Graph connector](https://learn.microsoft.com/graph/connecting-external-content-connectors-overview) that ingests data from a custom API to Microsoft Graph. It provides an end to end example of creating the connector, ingesting content and refreshing the ingested content on a schedule. It also includes the [simplified admin experience](https://learn.microsoft.com/graph/connecting-external-content-deploy-teams) which means that admins can toggle the connector on and off from the Microsoft Teams admin center.
+This sample project uses Microsoft 365 Agents Toolkit for Visual Studio Code to simplify the process of creating a [Microsoft Graph connector](https://learn.microsoft.com/graph/connecting-external-content-connectors-overview) that ingests data from a custom API to Microsoft Graph. It provides an end to end example of creating the connector, ingesting content and refreshing the ingested content on a schedule. It also includes the [simplified admin experience](https://learn.microsoft.com/graph/connecting-external-content-deploy-teams) which means that admins can toggle the connector on and off from the Microsoft Teams admin center.
 
 > ℹ️ Sample data is taken from [Open Food Facts API](https://openfoodfacts.github.io/openfoodfacts-server/api/).
 
@@ -17,7 +17,7 @@ This sample project uses Teams Toolkit for Visual Studio Code to simplify the pr
 
 Version|Date|Comments
 -------|----|--------
-1.9|February 21, 2025|Fixed for using latest version of Teams Toolkit
+1.9|February 21, 2025|Fixed for using latest version of Microsoft 365 Agents Toolkit
 1.8|October 01, 2024|Added support for provisioning and deploying to Azure
 1.7|September 2, 2024|Updated instructions
 1.6|August 13, 2024|Updated instructions
@@ -30,7 +30,7 @@ Version|Date|Comments
 
 ## Prerequisites
 
-- [Teams Toolkit for Visual Studio Code](https://marketplace.visualstudio.com/items?itemName=TeamsDevApp.ms-teams-vscode-extension)
+- [Microsoft 365 Agents Toolkit for Visual Studio Code](https://marketplace.visualstudio.com/items?itemName=TeamsDevApp.ms-teams-vscode-extension)
 - [Azure Functions Visual Studio Code extension](https://marketplace.visualstudio.com/items?itemName=ms-azuretools.vscode-azurefunctions)
 - [Microsoft 365 Developer tenant](https://developer.microsoft.com/microsoft-365/dev-program) with [uploading custom apps enabled](https://learn.microsoft.com/microsoftteams/platform/m365-apps/prerequisites#prepare-a-developer-tenant-for-testing)
 - [Dev Tunnels CLI](https://learn.microsoft.com/azure/developer/dev-tunnels/get-started#install)
@@ -106,11 +106,11 @@ When the process is complete you will see a table confirming that the connection
 
 ## Provision and deploy to Azure
 
-You can also provision and deploy the resources to Azure and publish the app to the Teams Admin Center using Teams Toolkit for Visual Studio Code.
+You can also provision and deploy the resources to Azure and publish the app to the Teams Admin Center using Microsoft 365 Agents Toolkit for Visual Studio Code.
 
 In Visual Studio Code:
 
-- Open Teams Toolkit from the sidebar
+- Open Microsoft 365 Agents Toolkit from the sidebar
 - In the Lifecycle section, select `Provision` and follow the prompts to provision the resources in Azure
 
 > [!NOTE]
@@ -141,7 +141,7 @@ This sample shows how to ingest data from a custom API into your Microsoft 365 t
 
 The sample illustrates the following concepts:
 
-- simplify debugging and provisioning of resources with Teams Toolkit for Visual Studio code
+- simplify debugging and provisioning of resources with Microsoft 365 Agents Toolkit for Visual Studio code
 - support the ability to toggle the connection status in the Microsoft Teams admin center
 - create external connection schema
 - support full ingestion of data

samples/nodejs-typescript-policies/.gitignore

@@ -17,7 +17,7 @@ __queuestorage__
 __azurite_db*__.json
 _storage_emulator
 
-# Teams Toolkit
+# Microsoft 365 Agents Toolkit
 build
 appPackage/build
 

samples/nodejs-typescript-policies/README.md

@@ -2,7 +2,7 @@
 
 ## Summary
 
-This sample project uses Teams Toolkit for Visual Studio Code to simplify the process of creating a [Microsoft Graph connector](https://learn.microsoft.com/graph/connecting-external-content-connectors-overview) that ingests data from a custom API to Microsoft Graph. It provides an end to end example of creating the connector, ingesting content and refreshing the ingested content.
+This sample project uses Microsoft 365 Agents Toolkit for Visual Studio Code to simplify the process of creating a [Microsoft Graph connector](https://learn.microsoft.com/graph/connecting-external-content-connectors-overview) that ingests data from a custom API to Microsoft Graph. It provides an end to end example of creating the connector, ingesting content and refreshing the ingested content.
 
 > [!NOTE]  
 > Sample data was generated using Artificial Intelligence. Any resemblance to real data is purely coincidental.
@@ -15,7 +15,7 @@ This sample shows how to ingest data from a custom API into your Microsoft 365 t
 
 The sample illustrates the following concepts:
 
-- simplify debugging and provisioning of resources with Teams Toolkit for Visual Studio code
+- simplify debugging and provisioning of resources with Microsoft 365 Agents Toolkit for Visual Studio code
 - create external connection schema
 - support full ingestion of data
 - visualize the external content in Microsoft 365 search results
@@ -36,7 +36,7 @@ Version|Date|Comments
 
 ## Prerequisites
 
-- [Teams Toolkit for Visual Studio Code](https://marketplace.visualstudio.com/items?itemName=TeamsDevApp.ms-teams-vscode-extension)
+- [Microsoft 365 Agents Toolkit for Visual Studio Code](https://marketplace.visualstudio.com/items?itemName=TeamsDevApp.ms-teams-vscode-extension)
 - [Azure Functions Visual Studio Code extension](https://marketplace.visualstudio.com/items?itemName=ms-azuretools.vscode-azurefunctions)
 - [Microsoft 365 Developer tenant](https://developer.microsoft.com/microsoft-365/dev-program) with [uploading custom apps enabled](https://learn.microsoft.com/microsoftteams/platform/m365-apps/prerequisites#prepare-a-developer-tenant-for-testing)
 - [Node@18](https://nodejs.org)

samples/nodejs-typescript-policies/teamsapp.yml → samples/nodejs-typescript-policies/m365agents.yml

@@ -46,7 +46,7 @@ provision:
           parameters: ./infra/azure.parameters.json
           # Required when deploying ARM template
           deploymentName: Create-resources-for-gc
-      # Teams Toolkit will download this bicep CLI version from github for you,
+      # Microsoft 365 Agents Toolkit will download this bicep CLI version from github for you,
       # will use bicep CLI in PATH if you remove this config.
       bicepCliVersion: v0.9.1