Skip to content

Commit 959ec7b

Browse files
Learn Build Service GitHub AppLearn Build Service GitHub App
Learn Build Service GitHub App
authored and
Learn Build Service GitHub App
committed
Merging changes synced from https://github.com/microsoftgraph/microsoft-graph-docs (branch live)
2 parents da876f1 + 422f6a6 commit 959ec7b

14 files changed

Lines changed: 427 additions & 50 deletions

‎api-reference/beta/resources/enums.md‎

Lines changed: 0 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -3737,14 +3737,6 @@ Possible values for user account types (group membership), per Windows definitio
37373737
| publication |
37383738
| unknownFutureValue |
37393739

3740-
### teamsAppInstallationScope values
3741-
3742-
| Member | Value | Description |
3743-
| --------- | ----- | --------------------------------------------------------------------------------------------------------------------------- |
3744-
| team | 0 | Indicates that the Teams app can be installed within a team and is authorized to access that team's data. |
3745-
| groupChat | 1 | Indicates that the Teams app can be installed within a group chat and is authorized to access that group chat's data. |
3746-
| personal | 2 | Indicates that the Teams app can be installed in the personal scope of a user and is authorized to access that user's data. |
3747-
37483740
### assignmentScheduleFilterByCurrentUserOptions values
37493741

37503742
| Member |

‎api-reference/beta/resources/groupchatteamsappinstallationscopeinfo.md‎

Lines changed: 44 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,44 @@
1+
---
2+
title: "groupChatTeamsAppInstallationScopeInfo resource type"
3+
description: "Represents the installation scope details when the Teams app is installed, updated, or deleted from a chat."
4+
author: "sthapliyal"
5+
ms.localizationpriority: medium
6+
ms.subservice: "teams"
7+
doc_type: resourcePageType
8+
ms.date: 06/05/2026
9+
---
10+
11+
# groupChatTeamsAppInstallationScopeInfo resource type
12+
13+
Namespace: microsoft.graph
14+
15+
[!INCLUDE [beta-disclaimer](../../includes/beta-disclaimer.md)]
16+
17+
Represents the installation scope details when the Teams app is installed, updated, or deleted from a [chat](../resources/chat.md).
18+
19+
Inherits from [teamsAppInstallationScopeInfo](../resources/teamsappinstallationscopeinfo.md).
20+
21+
## Properties
22+
23+
|Property|Type|Description|
24+
|:---|:---|:---|
25+
|chatId|String|The ID of the chat where the Teams app is installed.|
26+
|scope|teamsAppInstallationScopes|The scope in which the Teams app is installed. The possible values are: `team`, `groupChat`, `personal`, `unknownFutureValue`. Inherited from [teamsAppInstallationScopeInfo](../resources/teamsappinstallationscopeinfo.md).|
27+
28+
## JSON representation
29+
30+
The following JSON representation shows the resource type.
31+
32+
<!-- {
33+
"blockType": "resource",
34+
"@odata.type": "microsoft.graph.groupChatTeamsAppInstallationScopeInfo",
35+
"baseType": "microsoft.graph.teamsAppInstallationScopeInfo"
36+
}
37+
-->
38+
``` json
39+
{
40+
"@odata.type": "#microsoft.graph.groupChatTeamsAppInstallationScopeInfo",
41+
"chatId": "String",
42+
"scope": "String"
43+
}
44+
```

‎api-reference/beta/resources/personalteamsappinstallationscopeinfo.md‎

Lines changed: 44 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,44 @@
1+
---
2+
title: "personalTeamsAppInstallationScopeInfo resource type"
3+
description: "Represents the installation scope details when the Teams app is installed, updated, or deleted for a user."
4+
author: "sthapliyal"
5+
ms.localizationpriority: medium
6+
ms.subservice: "teams"
7+
doc_type: resourcePageType
8+
ms.date: 06/05/2026
9+
---
10+
11+
# personalTeamsAppInstallationScopeInfo resource type
12+
13+
Namespace: microsoft.graph
14+
15+
[!INCLUDE [beta-disclaimer](../../includes/beta-disclaimer.md)]
16+
17+
Represents the installation scope details when the Teams app is installed, updated, or deleted for a [user](../resources/user.md).
18+
19+
Inherits from [teamsAppInstallationScopeInfo](../resources/teamsappinstallationscopeinfo.md).
20+
21+
## Properties
22+
23+
|Property|Type|Description|
24+
|:---|:---|:---|
25+
|scope|teamsAppInstallationScopes|The scope in which the Teams app is updated, installed, or deleted. The possible values are: `team`, `groupChat`, `personal`, `unknownFutureValue`. Inherited from [teamsAppInstallationScopeInfo](../resources/teamsappinstallationscopeinfo.md).|
26+
|userId|String|The ID of the user for whom the Teams app is installed.|
27+
28+
## JSON representation
29+
30+
The following JSON representation shows the resource type.
31+
32+
<!-- {
33+
"blockType": "resource",
34+
"@odata.type": "microsoft.graph.personalTeamsAppInstallationScopeInfo",
35+
"baseType": "microsoft.graph.teamsAppInstallationScopeInfo"
36+
}
37+
-->
38+
``` json
39+
{
40+
"@odata.type": "#microsoft.graph.personalTeamsAppInstallationScopeInfo",
41+
"scope": "String",
42+
"userId": "String"
43+
}
44+
```

‎api-reference/beta/resources/teamsappdefinition.md‎

Lines changed: 12 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -26,9 +26,18 @@ The details of a version of a [teamsApp](teamsapp.md).
2626
| azureADAppId | string | The WebApplicationInfo.Id from the Teams app manifest. |
2727
| displayName | string | The name of the app provided by the app developer. |
2828
| version | string | The version number of the application. |
29-
| allowedInstallationScopes | teamsAppInstallationScope collection | A collection of scopes where the Teams app can be installed. The possible values are:</br>`team`—Indicates that the Teams app can be installed within a team and is authorized to access that team's data. </br>`groupChat`—Indicates that the Teams app can be installed within a group chat and is authorized to access that group chat's data.</br> `personal`—Indicates that the Teams app can be installed in the personal scope of a user and is authorized to access that user's data. |
29+
| allowedInstallationScopes | [teamsAppInstallationScopes](../resources/teamsappdefinition.md#teamsappinstallationscopes-values) collection | A collection of scopes where the Teams app can be installed. The possible values are:</br>`team`—Indicates that the Teams app can be installed within a team and is authorized to access that team's data. </br>`groupChat`—Indicates that the Teams app can be installed within a group chat and is authorized to access that group chat's data.</br> `personal`—Indicates that the Teams app can be installed in the personal scope of a user and is authorized to access that user's data. |
3030
|authorization|[teamsAppAuthorization](../resources/teamsappauthorization.md)|Authorization requirements specified in the Teams app manifest.|
3131

32+
### teamsAppInstallationScopes values
33+
34+
| Member | Description |
35+
| :--- | :--- |
36+
| team | Indicates that the Teams app can be installed within a team and is authorized to access that team data. |
37+
| groupChat | Indicates that the Teams app can be installed within a group chat and is authorized to access that group chat data. |
38+
| personal | Indicates that the Teams app can be installed in the personal scope of a user and is authorized to access that user data. |
39+
| unknownFutureValue | Evolvable enumeration sentinel value. Don't use.|
40+
3241
## Relationships
3342

3443
| Relationship | Type | Description |
@@ -56,7 +65,8 @@ The following JSON representation shows the resource type.
5665
"azureADAppId": "string",
5766
"displayName": "string",
5867
"version": "string",
59-
"authorization": "#microsoft.graph.teamsAppAuthorization"
68+
"authorization": "#microsoft.graph.teamsAppAuthorization",
69+
"allowedInstallationScopes": "String"
6070
}
6171
```
6272

‎api-reference/beta/resources/teamsappinstallation.md‎

Lines changed: 5 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -17,7 +17,7 @@ Namespace: microsoft.graph
1717
Represents a [teamsApp](teamsapp.md) installed in a [team](team.md), a [chat](chat.md), or the personal scope of a [user](user.md). Any bots that are part of the app become part of any team, chat, or user's personal scope that the app is added to.
1818

1919
> [!NOTE]
20-
> The `id` of a **teamsAppInstallation** resource is not the same value as the `id` of the associated **teamsApp** resource.
20+
> The **id** of a **teamsAppInstallation** resource isn't the same value as the **id** of the associated **teamsApp** resource.
2121
2222
## Methods
2323

@@ -45,6 +45,7 @@ Represents a [teamsApp](teamsapp.md) installed in a [team](team.md), a [chat](ch
4545
|:------------------- |:-------- |:----------- |
4646
|consentedPermissionSet|[teamsAppPermissionSet](../resources/teamsapppermissionset.md)|The set of resource-specific permissions consented to while installing or upgrading the teamsApp.|
4747
| id | string | A unique ID (not the team's app ID). |
48+
|scopeInfo|[teamsAppInstallationScopeInfo](../resources/teamsappinstallationscopeinfo.md)|The details of the scope in which the app is installed.|
4849

4950
## Relationships
5051

@@ -65,8 +66,9 @@ The following JSON representation shows the resource type.
6566

6667
```json
6768
{
68-
"consentedPermissionSet": "#microsoft.graph.teamsAppPermissionSet",
69-
"id": "string"
69+
"consentedPermissionSet": {"@odata.type": "#microsoft.graph.teamsAppPermissionSet"},
70+
"id": "string (identifier)",
71+
"scopeInfo": {"@odata.type": "#microsoft.graph.teamsAppInstallationScopeInfo"}
7072
}
7173
```
7274

‎api-reference/beta/resources/teamsappinstallationscopeinfo.md‎

Lines changed: 40 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,40 @@
1+
---
2+
title: "teamsAppInstallationScopeInfo resource type"
3+
description: "An abstract type that represents the details of the scope where the Teams app is installed."
4+
author: "sthapliyal"
5+
ms.localizationpriority: medium
6+
ms.subservice: "teams"
7+
doc_type: resourcePageType
8+
ms.date: 06/05/2026
9+
---
10+
11+
# teamsAppInstallationScopeInfo resource type
12+
13+
Namespace: microsoft.graph
14+
15+
[!INCLUDE [beta-disclaimer](../../includes/beta-disclaimer.md)]
16+
17+
An abstract type that represents the details of the scope where the Teams app is installed.
18+
19+
Base type of [groupChatTeamsAppInstallationScopeInfo](../resources/groupchatteamsappinstallationscopeinfo.md), [personalTeamsAppInstallationScopeInfo](../resources/personalteamsappinstallationscopeinfo.md), and [teamTeamsAppInstallationScopeInfo](../resources/teamteamsappinstallationscopeinfo.md).
20+
21+
## Properties
22+
23+
|Property|Type|Description|
24+
|:---|:---|:---|
25+
|scope|teamsAppInstallationScopes|The scope in which the Teams app is installed. The possible values are: `team`, `groupChat`, `personal`, `unknownFutureValue`.|
26+
27+
## JSON representation
28+
29+
The following JSON representation shows the resource type.
30+
<!-- {
31+
"blockType": "resource",
32+
"@odata.type": "microsoft.graph.teamsAppInstallationScopeInfo"
33+
}
34+
-->
35+
``` json
36+
{
37+
"@odata.type": "#microsoft.graph.teamsAppInstallationScopeInfo",
38+
"scope": "String"
39+
}
40+
```

‎api-reference/beta/resources/teamteamsappinstallationscopeinfo.md‎

Lines changed: 44 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,44 @@
1+
---
2+
title: "teamTeamsAppInstallationScopeInfo resource type"
3+
description: "Represents the installation scope details when the Teams app is installed in a team."
4+
author: "sthapliyal"
5+
ms.localizationpriority: medium
6+
ms.subservice: "teams"
7+
doc_type: resourcePageType
8+
ms.date: 06/05/2026
9+
---
10+
11+
# teamTeamsAppInstallationScopeInfo resource type
12+
13+
Namespace: microsoft.graph
14+
15+
[!INCLUDE [beta-disclaimer](../../includes/beta-disclaimer.md)]
16+
17+
Represents the installation scope details when the Teams app is installed in a [team](../resources/team.md).
18+
19+
Inherits from [teamsAppInstallationScopeInfo](../resources/teamsappinstallationscopeinfo.md).
20+
21+
## Properties
22+
23+
|Property|Type|Description|
24+
|:---|:---|:---|
25+
|scope|teamsAppInstallationScopes|The scope in which the Teams app is installed. The possible values are: `team`, `groupChat`, `personal`, `unknownFutureValue`. Inherited from [teamsAppInstallationScopeInfo](../resources/teamsappinstallationscopeinfo.md).|
26+
|teamId|String|The ID of the team where the Teams app is installed.|
27+
28+
## JSON representation
29+
30+
The following JSON representation shows the resource type.
31+
32+
<!-- {
33+
"blockType": "resource",
34+
"@odata.type": "microsoft.graph.teamTeamsAppInstallationScopeInfo",
35+
"baseType": "microsoft.graph.teamsAppInstallationScopeInfo"
36+
}
37+
-->
38+
``` json
39+
{
40+
"@odata.type": "#microsoft.graph.teamTeamsAppInstallationScopeInfo",
41+
"scope": "String",
42+
"teamId": "String"
43+
}
44+
```

‎api-reference/beta/toc/teamwork-and-communications/toc.yml‎

Lines changed: 8 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -246,6 +246,14 @@ items:
246246
items:
247247
- name: Custom app settings
248248
href: ../../resources/customappsettings.md
249+
- name: Group chat teams app installation scope info
250+
href: ../../resources/groupchatteamsappinstallationscopeinfo.md
251+
- name: Personal teams app installation scope info
252+
href: ../../resources/personalteamsappinstallationscopeinfo.md
253+
- name: Team teams app installation scope info
254+
href: ../../resources/teamteamsappinstallationscopeinfo.md
255+
- name: Teams app installation scope info
256+
href: ../../resources/teamsappinstallationscopeinfo.md
249257
- name: Calls and online meetings
250258
items:
251259
- name: Overview

‎api-reference/beta/toc/toc.mapping.json‎

Lines changed: 5 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -3445,7 +3445,11 @@
34453445
"resourceSpecificPermissionGrant"
34463446
],
34473447
"complexTypes": [
3448-
"customAppSettings"
3448+
"customAppSettings",
3449+
"groupChatTeamsAppInstallationScopeInfo",
3450+
"personalTeamsAppInstallationScopeInfo",
3451+
"teamsAppInstallationScopeInfo",
3452+
"teamTeamsAppInstallationScopeInfo"
34493453
]
34503454
},
34513455
{

‎api-reference/v1.0/resources/security-ediscovery-apioverview.md‎

Lines changed: 11 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -12,12 +12,17 @@ doc_type: conceptualPageType
1212

1313
The Microsoft Purview APIs for eDiscovery enable organizations to automate repetitive tasks and integrate with their existing eDiscovery tools to build repeatable workflows that industry regulations might require. You can use the eDiscovery APIs to help with your legal needs.
1414

15-
> [!IMPORTANT]
16-
> - The Microsoft Purview APIs for eDiscovery are intended for the use of eDiscovery operations for litigation, investigation, and regulatory requests. These APIs shouldn't be used as a substitute for journaling data out of the Microsoft 365 system or any other mass download.
17-
>
18-
> - For information about setting up app-only access, see [Set up application authentication](/graph/security-ediscovery-appauthsetup).
19-
>
20-
> - Usage of eDiscovery APIs in Microsoft Graph is subject to the same licensing and subscriptions for your organization that grant you access to standard or premium eDiscovery features in the Microsoft Purview portal. For more information, see [Learn about eDiscovery: Features and capabilities](/purview/edisc#features-and-capabilities).
15+
- The Microsoft Purview APIs for eDiscovery are intended for the use of eDiscovery operations for litigation, investigation, and regulatory requests. These APIs shouldn't be used as a substitute for journaling data out of the Microsoft 365 system or any other mass download.
16+
17+
- For information about setting up app-only access, see [Set up application authentication](/graph/security-ediscovery-appauthsetup).
18+
19+
- The eDiscovery APIs in Microsoft Graph are available to organizations with E3 and E5 subscriptions. The authentication method and available operations depend on your subscription tier. Organizations with an E3 subscription can use delegated (user) authentication to automate standard eDiscovery operations. App-only authentication and premium operations require E5 or an equivalent add-on subscription. For more information, see [Learn about eDiscovery: Features and capabilities](/purview/edisc#features-and-capabilities).
20+
21+
| Feature|E3/Standard with delegated auth|E5/Premium with delegated auth|E5/Premium with app-only auth|
22+
| -------- | -------- | -------- | -------- |
23+
|Cases, Searches, Holds|Yes |Yes|Yes|
24+
|Export|Requires pay-as-you-go billing|Yes|Yes|
25+
|Premium features incl: Review sets, tagging, analytics|No|Yes|Yes|
2126

2227
| Name | Type | Use case |
2328
|:---|:---|:---|

0 commit comments

Comments
 (0)