[Draft] [Doc's improvement] Update Teams manifest links

msteams-platform/apps-in-teams-meetings/app-icon-badging-for-your-app.md

@@ -36,7 +36,7 @@ To enable app icon badging, follow these steps:
 To enable app icon badging, you must:
 
 * Ensure that you've configured `meetingSidePanel` as a `context` property for your app.
-* Configure the `authorization` property and the `name` and `type` properties under the `resourceSpecific` field in the [app manifest](../resources/schema/manifest-schema.md#authorization) as follows:
+* Configure the `authorization` property and the `name` and `type` properties under the `resourceSpecific` field in the [app manifest](/microsoft-365/extensibility/schema/root-authorization) as follows:
 
 ```json
 

msteams-platform/apps-in-teams-meetings/build-apps-for-anonymous-user.md

@@ -35,7 +35,7 @@ To allow anonymous users to interact with the tab app, update the `supportsAnony
 }
 ```
 
-For more information, see [app manifest schema.](~/resources/schema/manifest-schema.md#meetingextensiondefinition)
+For more information, see [app manifest schema.](/microsoft-365/extensibility/schema/root-meeting-extension-definition)
 
 ## Anonymous user authentication flow
 

msteams-platform/apps-in-teams-meetings/build-apps-for-teams-meeting-stage.md

@@ -33,7 +33,7 @@ To invoke share to stage, users can select the **Share to Stage** icon on the up
 
 ### App manifest
 
-To share an app to the meeting stage, you must configure the context and Resource-specific consent (RSC) permissions in the [app manifest](../resources/schema/manifest-schema.md):
+To share an app to the meeting stage, you must configure the context and Resource-specific consent (RSC) permissions in the [app manifest](/microsoft-365/extensibility/schema/root-authorization-permissions-resource-specific):
 
 1. Update the `context` property in the app manifest as follows:
 
@@ -448,7 +448,7 @@ Follow the [step-by-step guide](../sbs-inmeeting-document-signing.yml) to build
 
 * [Apps for Teams meetings](teams-apps-in-meetings.md)
 * [Enable authentication using third-party OAuth provider](../tabs/how-to/authentication/auth-flow-tab.md)
-* [Resource-specific consent for delegated permissions](../resources/schema/manifest-schema.md#authorizationpermissions)
+* [Resource-specific consent for delegated permissions](/microsoft-365/extensibility/schema/root-authorization-permissions-resource-specific)
 * [Create deep links](../concepts/build-and-test/deep-links.md)
 * [Meeting app APIs](meeting-apps-apis.md)
 * [Custom Together Mode scenes](~/apps-in-teams-meetings/teams-together-mode.md)

msteams-platform/apps-in-teams-meetings/in-meeting-notification-for-meeting.md

@@ -79,7 +79,7 @@ In the following image, a meeting notification requesting payment is sent to one
 
 ### Enable app manifest settings for targeted in-meeting notification
 
-To send targeted in-meeting notifications, you must configure the `authorization` property and the `name` and `type` properties under the `resourceSpecific` field in the [app manifest](../resources/schema/manifest-schema.md#authorization) as follows:
+To send targeted in-meeting notifications, you must configure the `authorization` property and the `name` and `type` properties under the `resourceSpecific` field in the [app manifest](/microsoft-365/extensibility/schema/root-authorization-permissions-resource-specific) as follows:
 
 ```json
 

msteams-platform/apps-in-teams-meetings/meeting-apps-apis.md

@@ -833,7 +833,7 @@ The `targetedMeetingNotification` API allows apps to send targeted in-meeting no
 
 ### Prerequisite
 
-You must configure your [app manifest](../resources/schema/manifest-schema.md) with [RSC permissions](../graph-api/rsc/resource-specific-consent.md) under the `webApplicationInfo` property to send targeted in-meeting notifications and shows app icon badging to specific participants in a meeting. Use the following examples to configure your manifest:
+You must configure your [app manifest](/microsoft-365/extensibility/schema/root-authorization-permissions-resource-specific) with [RSC permissions](../graph-api/rsc/resource-specific-consent.md) under the `webApplicationInfo` property to send targeted in-meeting notifications and shows app icon badging to specific participants in a meeting. Use the following examples to configure your manifest:
 
 <br>
 

msteams-platform/apps-in-teams-meetings/teams-live-share-how-to/how-to-custom-azure-fluid-relay.md

@@ -369,4 +369,4 @@ Many Live Share APIs depend on a global timestamp API, which allows `LiveDataObj
 * [Live Share Media SDK reference docs](/javascript/api/@microsoft/live-share-media/)
 * [Live Share FAQ](../teams-live-share-faq.md)
 * [Use Fluid with Teams](../../tabs/how-to/using-fluid-msteam.md)
-* [App manifest schema for Teams](../../resources/schema/manifest-schema.md)
+* [App manifest schema for Teams](/microsoft-365/extensibility/schema)

msteams-platform/apps-in-teams-meetings/teams-live-share-media-capabilities.md

@@ -554,4 +554,4 @@ Additionally, add the following [RSC](/microsoftteams/platform/graph-api/rsc/res
 - [Live Share SDK reference docs](/javascript/api/@microsoft/live-share/)
 - [Live Share Media SDK reference docs](/javascript/api/@microsoft/live-share-media/)
 - [Use Fluid with Teams](../tabs/how-to/using-fluid-msteam.md)
-- [App manifest schema for Teams](../resources/schema/manifest-schema.md)
+- [App manifest schema for Teams](/microsoft-365/extensibility/schema)

msteams-platform/apps-in-teams-meetings/teams-live-share-tutorial.md

@@ -78,6 +78,7 @@ async function start() {
 
 start().catch((error) => console.error(error));
 ```
+
 > [!div class="nextstepaction"]
 > [I ran into an issue](https://github.com/MicrosoftDocs/msteams-docs/issues/new?template=Doc-Feedback.yaml&title=%5BI+ran+into+an+issue%5D+Set+up+the+application&&author=%40surbhigupta&pageUrl=https%3A%2F%2Flearn.microsoft.com%2Fen-us%2Fmicrosoftteams%2Fplatform%2Fapps-in-teams-meetings%2Fteams-live-share-tutorial%23set-up-the-application&contentSourceUrl=https%3A%2F%2Fgithub.com%2FMicrosoftDocs%2Fmsteams-docs%2Fblob%2Fmain%2Fmsteams-platform%2Fapps-in-teams-meetings%2Fteams-live-share-tutorial.md&documentVersionIndependentId=c4095988-9b54-4919-411d-4db9b081af57&platformId=c94461f7-1c1f-7cac-ba73-b2982d5b6cb6&metadata=*%2BID%253A%2Be473e1f3-69f5-bcfa-bcab-54b098b59c80%2B%250A*%2BService%253A%2B%2A%2Amsteams%2A%2A)
 
@@ -184,6 +185,7 @@ After you initialize `LiveState`, the `stateChanged` event you registered earlie
 await diceState.initialize(1);
 updateDice();
 ```
+
 > [!div class="nextstepaction"]
 > [I ran into an issue](https://github.com/MicrosoftDocs/msteams-docs/issues/new?template=Doc-Feedback.yaml&title=%5BI+ran+into+an+issue%5D+Connect+meeting+Stageview+to+Live+Share&&author=%40surbhigupta&pageUrl=https%3A%2F%2Flearn.microsoft.com%2Fen-us%2Fmicrosoftteams%2Fplatform%2Fapps-in-teams-meetings%2Fteams-live-share-tutorial%23connect-meeting-stageview-to-live-share&contentSourceUrl=https%3A%2F%2Fgithub.com%2FMicrosoftDocs%2Fmsteams-docs%2Fblob%2Fmain%2Fmsteams-platform%2Fapps-in-teams-meetings%2Fteams-live-share-tutorial.md&documentVersionIndependentId=c4095988-9b54-4919-411d-4db9b081af57&platformId=c94461f7-1c1f-7cac-ba73-b2982d5b6cb6&metadata=*%2BID%253A%2Be473e1f3-69f5-bcfa-bcab-54b098b59c80%2B%250A*%2BService%253A%2B%2A%2Amsteams%2A%2A)
 
@@ -215,7 +217,7 @@ function renderSidePanel(elem) {
 
 ## Write the settings view
 
-The settings view, loaded through `configurationUrl` in your [app manifest](../resources/schema/manifest-schema.md#configurabletabs), is shown to a user when they first add your app to a Teams meeting. This view lets the developer configure the `contentUrl` for the tab that is pinned to the meeting based on user input. This page is required even if no user input is required to set the `contentUrl`.
+The settings view, loaded through `configurationUrl` in your [app manifest](/microsoft-365/extensibility/schema/root-configurable-tabs#configurationurl), is shown to a user when they first add your app to a Teams meeting. This view lets the developer configure the `contentUrl` for the tab that is pinned to the meeting based on user input. This page is required even if no user input is required to set the `contentUrl`.
 
 > [!NOTE]
 > The Live Share's' `joinContainer()` is not supported in the tab `settings` context.
@@ -303,7 +305,7 @@ After you start running your app locally with `npm run start`, you can then test
    > - Don't zip the containing folder.
    > - Give your zip file a descriptive name. For example, `DiceRollerLiveShare`.
 
-   For more information on manifest, visit the [Teams manifest documentation](../resources/schema/manifest-schema.md)
+   For more information on manifest, visit the [Teams manifest documentation](/microsoft-365/extensibility/schema)
 
 > [!div class="nextstepaction"]
 > [I ran into an issue](https://github.com/MicrosoftDocs/msteams-docs/issues/new?template=Doc-Feedback.yaml&title=%5BI+ran+into+an+issue%5D+Create+the+app+package+to+upload+into+Teams&&author=%40surbhigupta&pageUrl=https%3A%2F%2Flearn.microsoft.com%2Fen-us%2Fmicrosoftteams%2Fplatform%2Fapps-in-teams-meetings%2Fteams-live-share-tutorial%23create-the-app-package-to-upload-into-teams&contentSourceUrl=https%3A%2F%2Fgithub.com%2FMicrosoftDocs%2Fmsteams-docs%2Fblob%2Fmain%2Fmsteams-platform%2Fapps-in-teams-meetings%2Fteams-live-share-tutorial.md&documentVersionIndependentId=c4095988-9b54-4919-411d-4db9b081af57&platformId=c94461f7-1c1f-7cac-ba73-b2982d5b6cb6&metadata=*%2BID%253A%2Be473e1f3-69f5-bcfa-bcab-54b098b59c80%2B%250A*%2BService%253A%2B%2A%2Amsteams%2A%2A)
@@ -351,9 +353,9 @@ Users invited to the meeting can see your app on stage when they join the meetin
 
 After you're ready to deploy your code, you can use Microsoft 365 Agents Toolkit (previously known as Teams Toolkit) or Developer Portal to provision and upload your app's zip file. To learn more about publishing and deploying your Teams app, see the following resources:
 
-* [Publish your app using Agents Toolkit for Visual Studio Code](../toolkit/publish.md).
-* [Publish your app using Developer Portal](../toolkit/publish-your-teams-apps-using-developer-portal.md).
-* [Deploy your app with Agents Toolkit for Visual Studio](../toolkit/toolkit-v4/deploy-vs.md).
+- [Publish your app using Agents Toolkit for Visual Studio Code](../toolkit/publish.md).
+- [Publish your app using Developer Portal](../toolkit/publish-your-teams-apps-using-developer-portal.md).
+- [Deploy your app with Agents Toolkit for Visual Studio](../toolkit/toolkit-v4/deploy-vs.md).
 
 > [!NOTE]
 > You need to add your provisioned appId to the `manifest.json` before uploading or distributing the app.

msteams-platform/bots/build-conversational-capability.md

@@ -238,7 +238,7 @@ The **Read receipts** setting in Teams allow the sender of a chat message to be
 
 To receive read receipts events for your bot, ensure the following:
 
-- Add the [RSC](~/graph-api/rsc/resource-specific-consent.md#rsc-permissions-for-a-chat-or-meeting) `ChatMessageReadReceipt.Read.Chat` permission in the [app manifest](~/resources/schema/manifest-schema.md), as follows:
+- Add the [RSC](~/graph-api/rsc/resource-specific-consent.md#rsc-permissions-for-a-chat-or-meeting) `ChatMessageReadReceipt.Read.Chat` permission in the [app manifest](/microsoft-365/extensibility/schema/root-authorization-permissions-resource-specific#rsc-delegated-permissionsd), as follows:
 
   # [App manifest v1.12 or later](#tab/app-manifest-v112-or-later)
 

msteams-platform/bots/calls-and-meetings/calls-meetings-bots-overview.md

@@ -18,7 +18,7 @@ To use these Graph APIs in a Teams app, you create a bot and specify some additi
 
 In addition, the Real-time Media Platform enables bots to interact with Teams calls and meetings using real-time voice, video, and screen sharing. A bot that participates in audio or video calls and online meetings is a regular Microsoft Teams bot with few extra features used to register the bot.
 
-The Teams [app manifest](../../resources/schema/manifest-schema.md#bots) with two more settings `supportsCalling` and `supportsVideo`, Graph permissions for your bot's Microsoft App ID, and admin consent enables you to register the bot. In registering a calls and meetings bot for Teams, the Webhook URL is mentioned, which is the webhook endpoint for all incoming calls to your bot. An application-hosted media bot requires the Microsoft.Graph.Communications.Calls.Media .NET library to access the audio and video media streams, and the bot must be deployed on a Windows Server machine or Windows Server guest Operating System (OS) in Azure. Bots on Teams support only a specific set of media formats for audio and video content.
+The Teams [app manifest](/microsoft-365/extensibility/schema/root-bots) with two more settings `supportsCalling` and `supportsVideo`, Graph permissions for your bot's Microsoft App ID, and admin consent enables you to register the bot. In registering a calls and meetings bot for Teams, the Webhook URL is mentioned, which is the webhook endpoint for all incoming calls to your bot. An application-hosted media bot requires the Microsoft.Graph.Communications.Calls.Media .NET library to access the audio and video media streams, and the bot must be deployed on a Windows Server machine or Windows Server guest Operating System (OS) in Azure. Bots on Teams support only a specific set of media formats for audio and video content.
 
 ## Functions of calls and online meeting bots
 

msteams-platform/bots/calls-and-meetings/registering-calling-bot.md

@@ -9,7 +9,7 @@ ms.date: 11/23/2022
 
 A bot that participates in audio or video calls and online meetings is a regular Microsoft Teams bot with the following extra features used to register the bot:
 
-* There's a new version of app manifest (previously called Teams app manifest) with two additional settings, `supportsCalling` and `supportsVideo`. These settings are included in the [app manifest](../../resources/schema/manifest-schema.md#bots).
+* There's a new version of app manifest (previously called Teams app manifest) with two additional settings, `supportsCalling` and `supportsVideo`. These settings are included in the [app manifest](/microsoft-365/extensibility/schema/root-bots).
 * [Microsoft Graph permissions](./registering-calling-bot.md#add-graph-permissions) must be configured for your bot's Microsoft App ID.
 * The Graph calls and online meetings APIs permissions require admin consent.
 

msteams-platform/bots/how-to/authentication/add-authentication.md

@@ -297,7 +297,7 @@ With the preliminary settings done, let's focus on the creation of the bot to us
 
      [!code-json[appsettings](~/../Microsoft-Teams-Samples/samples/bot-teams-authentication/csharp/appsettings.json?range=1-5)]
 
-1. In the Solution Explorer, go to the `TeamsAppManifest` folder, open `manifest.json` and set `id` and `botId` to the **bot App ID** you saved at the time of the bot registration. For more information, see [app manifest](../../../resources/schema/manifest-schema.md#bots).
+1. In the Solution Explorer, go to the `TeamsAppManifest` folder, open `manifest.json` and set `id` and `botId` to the **bot App ID** you saved at the time of the bot registration. For more information, see [app manifest](/microsoft-365/extensibility/schema/root-bots#botid).
 
 > [!div class="nextstepaction"]
 > [I ran into an issue](https://github.com/MicrosoftDocs/msteams-docs/issues/new?template=Doc-Feedback.yaml&title=%5BI+ran+into+an+issue%5D+Prepare+the+bot+sample+code+using+C%23%2F.NET&&author=%40surbhigupta&pageUrl=https%3A%2F%2Flearn.microsoft.com%2Fen-us%2Fmicrosoftteams%2Fplatform%2Fbots%2Fhow-to%2Fauthentication%2Fadd-authentication%3Ftabs%3Dnode-js%252Cdotnet-sample%23test-the-connection&contentSourceUrl=https%3A%2F%2Fgithub.com%2FMicrosoftDocs%2Fmsteams-docs%2Fblob%2Fmain%2Fmsteams-platform%2Fbots%2Fhow-to%2Fauthentication%2Fadd-authentication.md&documentVersionIndependentId=70952f91-56e9-ff08-59f6-e237d4aaeca9&platformId=cc53b20b-69e0-cb70-1ca7-9b939c969c92&metadata=*%2BID%253A%2Be473e1f3-69f5-bcfa-bcab-54b098b59c80%2B%250A*%2BService%253A%2B%2A%2Amsteams%2A%2A)

msteams-platform/bots/how-to/authentication/bot-sso-manifest.md

@@ -31,7 +31,7 @@ Configure the `webApplicationInfo` property in the app manifest file. This prope
 
 The application ID URI that you registered in Microsoft Entra ID is configured with the scope of the API you exposed. Configure your app's subdomain URI in `resource` to ensure that the authentication request using `getAuthToken()` is from the domain given in app manifest.
 
-For more information, see [webApplicationInfo](../../../resources/schema/manifest-schema.md#webapplicationinfo).
+For more information, see [webApplicationInfo](/microsoft-365/extensibility/schema/root-web-application-info).
 
 ## To configure app manifest
 
@@ -41,7 +41,7 @@ For more information, see [webApplicationInfo](../../../resources/schema/manifes
     > [!NOTE]
     >
     > - The app manifest folder should be at the root of your project. For more information, see [Create a Microsoft Teams app package](../../../concepts/build-and-test/apps-package.md).
-    > - For more information on learning how to create a manifest.json, see [the app manifest schema for Microsoft Teams](../../../resources/schema/manifest-schema.md).
+    > - For more information on learning how to create a manifest.json, see [the app manifest schema for Microsoft Teams](/microsoft-365/extensibility/schema/).
 
 1. Open the `manifest.json` file.
 1. Add one of the following code snippets to the app manifest file to add the new property:
@@ -79,7 +79,7 @@ For more information, see [webApplicationInfo](../../../resources/schema/manifes
    > [!NOTE]
    > To handle authentication and token exchange, add `https://token.botframework.com` to the `validDomains` property for bots using Bot Framework. For OAuth URLs and data residency list, see [OAuth URL support in Azure AI Bot Service](/azure/bot-service/ref-oauth-redirect-urls?view=azure-bot-service-4.0&preserve-view=true).
 
-6. Save the app manifest file. For more information, see [app manifest](../../../resources/schema/manifest-schema.md).
+6. Save the app manifest file. For more information, see [app manifest](/microsoft-365/extensibility/schema/).
 
 <br>
 <details>

msteams-platform/bots/how-to/bot-configuration-experience.md

@@ -72,7 +72,7 @@ In the app manifest (previously called Teams app manifest) file, update the `fet
   ],
 ```
 
-For more information, see [app manifest schema](../../resources/schema/manifest-schema.md#botsconfiguration).
+For more information, see [app manifest schema](/microsoft-365/extensibility/schema/root-bots-configuration).
 
 > [!div class="nextstepaction"]
 > [I ran into an issue](https://github.com/MicrosoftDocs/msteams-docs/issues/new?template=Doc-Feedback.yaml&title=%5BI+ran+into+an+issue%5D+Update+app+manifest&&author=%40surbhigupta&pageUrl=https%3A%2F%2Flearn.microsoft.com%2Fen-us%2Fmicrosoftteams%2Fplatform%2Fbots%2Fhow-to%2Fbot-configuration-experience%3Ftabs%3Dteams-bot-sdk1%252Cteams-bot-sdk2%252Cteams-bot-sdk3%23update-app-manifest&contentSourceUrl=https%3A%2F%2Fgithub.com%2FMicrosoftDocs%2Fmsteams-docs%2Fblob%2Fmain%2Fmsteams-platform%2Fbots%2Fhow-to%2Fbot-configuration-experience.md&documentVersionIndependentId=415c2389-14be-5efd-9542-a58bf8a03900&platformId=7be118d5-e34d-24a2-73f8-81d8ec7c3cdf&metadata=*%2BID%253A%2Be473e1f3-69f5-bcfa-bcab-54b098b59c80%2B%250A*%2BService%253A%2B%2A%2Amsteams%2A%2A)

msteams-platform/bots/how-to/bots-filesv4.md

@@ -49,7 +49,7 @@ The next sections describe how to send file content as direct user interaction,
 
 ### Configure the bot to support files
 
-To send and receive files in the bot, set the `supportsFiles` property in the manifest to `true`. This property is described in the [bots](~/resources/schema/manifest-schema.md#bots) section of the manifest reference.
+To send and receive files in the bot, set the `supportsFiles` property in the manifest to `true`. This property is described in the [bots](/microsoft-365/extensibility/schema/root-bots#supportsfiles) section of the manifest reference.
 
 The definition looks like this, `"supportsFiles": true`. If the bot does not enable `supportsFiles`, the features listed in this section do not work.
 

msteams-platform/bots/how-to/conversations/channel-messages-for-bots-and-agents.md

@@ -85,7 +85,7 @@ For example, use RSC permissions for an AI agent to manage channel content.
 
 ## Update app manifest
 
-For your bot or agent to receive all conversation messages, specify the relevant RSC permission strings in the `authorization.permissions.resourceSpecific` property of your app manifest. For more information, see [app manifest schema](../../../resources/schema/manifest-schema.md).
+For your bot or agent to receive all conversation messages, specify the relevant RSC permission strings in the `authorization.permissions.resourceSpecific` property of your app manifest. For more information, see [app manifest schema](/microsoft-365/extensibility/schema/root-authorization-permissions).
 
 Here's an app manifest example followed by a sample code snippet:
 

msteams-platform/bots/how-to/conversations/command-bot-in-teams.md

@@ -133,7 +133,7 @@ You can edit the manifest template file `appPackage\manifest.json` to update the
 ]
 ```
 
-For more information, see [app manifest](../../../resources/schema/manifest-schema.md#botscommandlistscommands).
+For more information, see [app manifest](/microsoft-365/extensibility/schema/root-bots-command-lists-commands).
 
 <br>
 </details>