Difference in webApplicationInfo.resource Configuration and Its Impact on microsoftTeams.authentication.getAuthToken() Behavior

[asith-w]

Issue:

Below are two configurations of the webApplicationInfo property from the Teams app manifest:

Configuration 1:

{
  "webApplicationInfo": { 
    "id": "1234b47a-0d54-0000-1111-92940bc85c11",
    "resource": "api://mydmn.net/botid-1234b47a-0d54-0000-1111-92940bc85c11"
  }
}

Configuration 2:

{
  "webApplicationInfo": { 
    "id": "1234b47a-0d54-0000-1111-92940bc85c11",
    "resource": "api://mydmn.net/1234b47a-0d54-0000-1111-92940bc85c11"
  }
}

Key Question:

The difference between the two configurations lies in the resource property:

1. Configuration 1 includes the botid- prefix in the resource value.
2. Configuration 2 excludes the botid- prefix.

Why does the microsoftTeams.authentication.getAuthToken() function behave differently for these configurations, as described in GitHub Issue #2196?

Request:
could anybody clarify the difference between these two configurations and explain how the resource value affects authentication behavior. Additionally, it would be helpful to understand the expected behavior for both scenarios and the correct way to configure the webApplicationInfo property to ensure consistent functionality.

[Meghana-MSFT]

@asith-w - Thank you for reporting this, we will check this and get back to you.

[Meghana-MSFT]

@asith-w - You can use configuration 2 if your app is only a tab app.

You can use configuration 1, if you're building an app with a bot, a messaging extension, and a tab.

[asith-w]

@Meghana-MSFT Thank you for the reply .

Is there a specific reason why the Teams app development maintains these two formats of URI (why can't those have same ability)?
Will both URI formats offer the same capabilities in the future?

[Meghana-MSFT]

@asith-w - We currently do not have any info if both URI formats will offer the same capabilities in the future. The doc will be updated if there are any updates to this in future. You can also subscribe to RSS feed to get latest Teams platform updates
What's new - Teams | Microsoft Docs