Skip to content

Commit 3190c54

Browse files
DanielabomDanielabom
authored
Merge branch 'main' into FaithOmbongi-patch-2
2 parents 0078071 + a669205 commit 3190c54

16 files changed

+447
-20
lines changed

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

Lines changed: 55 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,55 @@
1+
---
2+
title: "callEvent resource type"
3+
description: "Contains information about a call event."
4+
author: "awang119"
5+
ms.localizationpriority: medium
6+
ms.subservice: "cloud-communications"
7+
ms.date: 12/03/2024
8+
doc_type: resourcePageType
9+
---
10+
11+
# callEvent resource type
12+
13+
Namespace: microsoft.graph
14+
15+
[!INCLUDE [beta-disclaimer](../../includes/beta-disclaimer.md)]
16+
17+
Contains information about a call event. The call can be a one-on-one or group ad-hoc call, a PSTN or VOIP call, or a scheduled active online meeting.
18+
19+
## Methods
20+
21+
None.
22+
23+
## Properties
24+
|Property|Type|Description|
25+
|:---|:---|:---|
26+
| callEventType | callEventType| The event type of the call. Possible values are: `callStarted`, `callEnded`, `unknownFutureValue`, `rosterUpdated`. You must use the `Prefer: include-unknown-enum-members` request header to get the following value in this [evolvable enum](/graph/best-practices-concept#handling-future-members-in-evolvable-enumerations): `rosterUpdated`.|
27+
| eventDateTime | DateTimeOffset | The time when event occurred. |
28+
| id | String | The unique identifier for the call event. |
29+
30+
## Relationships
31+
|Relationship|Type|Description|
32+
|:---|:---|:---|
33+
| participants | [participant](../resources/participant.md) collection| Participants collection for the call event. |
34+
35+
## JSON representation
36+
The following JSON representation shows the resource type.
37+
<!-- {
38+
"blockType": "resource",
39+
"keyProperty": "id",
40+
"@odata.type": "microsoft.graph.callEvent",
41+
"openType": false
42+
}
43+
-->
44+
``` json
45+
{
46+
"@odata.type": "#microsoft.graph.callEvent",
47+
"id": "String (identifier)",
48+
"callEventType": "String",
49+
"eventDateTime": "String (timestamp)",
50+
}
51+
```
52+
53+
## Related content
54+
55+
[Change notification for active meeting call events](/graph/changenotifications-for-onlinemeeting)

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

Lines changed: 49 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,49 @@
1+
---
2+
title: "emergencyCallerInfo resource type"
3+
description: "Contains information about an emergency caller."
4+
author: "awang119"
5+
ms.localizationpriority: medium
6+
ms.subservice: "cloud-communications"
7+
ms.date: 12/03/2024
8+
doc_type: resourcePageType
9+
---
10+
# emergencyCallerInfo resource type
11+
12+
Namespace: microsoft.graph
13+
14+
[!INCLUDE [beta-disclaimer](../../includes/beta-disclaimer.md)]
15+
16+
Contains information about the emergency caller.
17+
18+
## Properties
19+
|Property|Type|Description|
20+
|:---|:---|:---|
21+
| displayName | String | The display name of the emergency caller. |
22+
| location | [location](../resources/location.md) | The location of the emergency caller. |
23+
| phoneNumber | String | The phone number of the emergency caller. |
24+
| tenantId | String | The tenant ID of the emergency caller. |
25+
| upn | String | The user principal name of the emergency caller. |
26+
27+
## Relationships
28+
None.
29+
30+
## JSON representation
31+
The following JSON representation shows the resource type.
32+
<!-- {
33+
"blockType": "resource",
34+
"@odata.type": "microsoft.graph.emergencyCallerInfo"
35+
}
36+
-->
37+
``` json
38+
{
39+
"@odata.type": "#microsoft.graph.emergencyCallerInfo",
40+
"displayName": "String",
41+
"upn": "String",
42+
"phoneNumber": "String",
43+
"tenantId": "String",
44+
"location": {
45+
"@odata.type": "microsoft.graph.location"
46+
}
47+
}
48+
```
49+

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

Lines changed: 66 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,66 @@
1+
---
2+
title: "emergencyCallEvent resource type"
3+
description: "Contains information about an emergency call event."
4+
author: "awang119"
5+
ms.localizationpriority: medium
6+
ms.subservice: "cloud-communications"
7+
ms.date: 12/03/2024
8+
doc_type: resourcePageType
9+
---
10+
11+
# emergencyCallEvent resource type
12+
13+
Namespace: microsoft.graph
14+
15+
[!INCLUDE [beta-disclaimer](../../includes/beta-disclaimer.md)]
16+
17+
Contains information about an emergency call event.
18+
19+
Inherits from [callEvent](../resources/callevent.md).
20+
21+
## Methods
22+
23+
None.
24+
25+
## Properties
26+
|Property|Type|Description|
27+
|:---|:---|:---|
28+
| callerInfo | [emergencyCallerInfo](../resources/emergencycallerinfo.md)| The information of the emergency caller. |
29+
| callEventType | callEventType| The event type of the call. Possible values are: `callStarted`, `callEnded`, `unknownFutureValue`, `rosterUpdated`. You must use the `Prefer: include-unknown-enum-members` request header to get the following value in this [evolvable enum](/graph/best-practices-concept#handling-future-members-in-evolvable-enumerations): `rosterUpdated`.|
30+
| emergencyNumberDialed | String | The emergency number dialed. |
31+
| eventDateTime | DateTimeOffset | The time of when event occurred. |
32+
| id | String | The entity ID. |
33+
| policyName | String | The policy name for emergency call event. |
34+
35+
## Relationships
36+
|Relationship|Type|Description|
37+
|:---|:---|:---|
38+
| participants | [participant](../resources/participant.md) collection| Participants aren't defined for emergency call events. Inherited from [microsoft.graph.callEvent](../resources/callevent.md). |
39+
40+
## JSON representation
41+
The following JSON representation shows the resource type.
42+
<!-- {
43+
"blockType": "resource",
44+
"keyProperty": "id",
45+
"@odata.type": "microsoft.graph.emergencyCallEvent",
46+
"baseType": "microsoft.graph.callEvent",
47+
"openType": false
48+
}
49+
-->
50+
``` json
51+
{
52+
"@odata.type": "#microsoft.graph.emergencyCallEvent",
53+
"id": "String (identifier)",
54+
"callEventType": "String",
55+
"eventDateTime": "String (timestamp)",
56+
"policyName": "String",
57+
"emergencyNumberDialed": "String",
58+
"callerInfo": {
59+
"@odata.type": "microsoft.graph.emergencyCallerInfo"
60+
}
61+
}
62+
```
63+
64+
## Related content
65+
66+
[Change notification for emergency call events](/graph/changenotifications-for-emergencycalls)

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

Lines changed: 10 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -3423,6 +3423,7 @@ Possible values for user account types (group membership), per Windows definitio
34233423
| project |
34243424
| driveItem |
34253425
| user |
3426+
| teamsChannel|
34263427

34273428
### plannerPlanContextType values
34283429

@@ -4990,6 +4991,15 @@ Possible values for user account types (group membership), per Windows definitio
49904991
| all |
49914992
| unknownFutureValue |
49924993

4994+
### callEventType values
4995+
4996+
| Member |
4997+
| ------------------ |
4998+
| callStarted |
4999+
| callEnded |
5000+
| unknownFutureValue |
5001+
| rosterUpdated |
5002+
49935003
### restoreArtifactsBulkRequestStatus values
49945004

49955005
|Member|

‎api-reference/beta/resources/planner-overview.md

Lines changed: 26 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -17,7 +17,7 @@ You can use the Planner API in Microsoft Graph to create tasks and assign them t
1717
Before you get started with the Planner API, it's helpful to understand how the main objects relate to each other and to Microsoft 365 groups.
1818

1919
## Plan containers
20-
In Microsoft Planner, plans are always contained in another resource. The containing resource, [plannerPlanContainer](plannerplancontainer.md), determines the authorization rules of the plan and all the tasks in it, and the lifecycle of the plan. You can create a plan in a container of one of the following types: [driveItem](driveitem.md), Microsoft 365 [group](group.md), Planner project, [roster](plannerroster.md), or [user](user.md).
20+
In Microsoft Planner, plans are always contained in another resource. The containing resource, [plannerPlanContainer](plannerplancontainer.md), determines the authorization rules of the plan and all the tasks in it, and the lifecycle of the plan. You can create a plan in a container of one of the following types: [driveItem](driveitem.md), Microsoft 365 [group](group.md), Planner project, [roster](plannerroster.md), [teamsChannel](channel.md), or [user](user.md).
2121

2222
The most common type of container is a group.
2323

@@ -35,8 +35,32 @@ GET /groups/{group-id}/planner/plans
3535

3636
When you [create a new plan](../api/planner-post-plans.md), set the **container** property on a plan object to make a group its container. Plans must be contained by a supported resource.
3737

38-
>**Note:** The user who is creating the plan must be a member of the group that will contain the plan. When you create a new group by using [Create group](../api/group-post-groups.md), you are not added to the group as a member. After the group is created, add yourself as a member by using [group post members](../api/group-post-members.md).
38+
>**Note:** The user who creates the plan must be a member of the group that contains the plan. When you create a new group by using [Create group](../api/group-post-groups.md), you aren't added to the group as a member. After the group is created, add yourself as a member by using [group post members](../api/group-post-members.md).
3939
40+
### Container type: Teams channel
41+
42+
The `teamsChannel` container type supports plans created in shared channels in Teams, where the channel is the container for the plan. Plans that are pinned in shared channels are deleted when the channel is deleted.
43+
44+
To [create a new plan](../api/planner-post-plans.md) in the container of a Teams channel, set the **container** property on a [plan](plannerplan.md) object with **type** as `teamsChannel`, and the ID should be formatted as "{team-id}/channels/{channel-id}".
45+
46+
```json
47+
{
48+
"container": {
49+
"id": "{team-id}/channels/{channel-id}",
50+
"type": "teamsChannel"
51+
}
52+
}
53+
```
54+
55+
Alternatively, you can specify the URL for a shared channel in Teams.
56+
57+
```json
58+
{
59+
"container": {
60+
"url": "https://graph.microsoft.com/beta/teams/{team-id}/channels/{channel-id}"
61+
}
62+
}
63+
```
4064

4165
### Container type: User
4266

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

Lines changed: 7 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -20,24 +20,25 @@ Planner currently supports the container types listed in the following table. Wh
2020

2121
|Type|Description|Path to the resource|
2222
|----|-----------|--------------------|
23+
|driveItem| Plan is contained by a [driveItem](driveitem.md). | `https://graph.microsoft.com/beta/drives/<driveId>/items/<itemId>`|
2324
|group| Plan is contained by a [group](group.md).| `https://graph.microsoft.com/beta/groups/<id>` |
24-
|roster| Plan is contained by a [plannerRoster](plannerroster.md). | `https://graph.microsoft.com/beta/planner/rosters/<id>` |
2525
|project| Plan is contained by a Project from [Microsoft Project for the web](/project-for-the-web/projectforweb-admin-home). | Microsoft Project currently doesn't have a resource path on Microsoft Graph. Project details and members can be managed from [Microsoft Project](https://project.microsoft.com). |
26-
|driveItem| Plan is contained by a [driveItem](driveitem.md). | `https://graph.microsoft.com/beta/drives/<driveId>/items/<itemId>`|
26+
|roster| Plan is contained by a [plannerRoster](plannerroster.md). | `https://graph.microsoft.com/beta/planner/rosters/<id>` |
27+
|teamsChannel| Plan is contained by a Teams [channel](channel.md). | `https://graph.microsoft.com/beta/teams/<teamId>/channels/<channelId>` |
2728
|user| Plan is contained by a [User](user.md) | `https://graph.microsoft.com/beta/users/<id>` |
2829

2930
## Properties
3031
|Property|Type|Description|
3132
|:---|:---|:---|
3233
|containerId|String|The identifier of the resource that contains the plan. Optional.|
33-
|type|plannerContainerType|The type of the resource that contains the plan. For supported types, see the previous table. Possible values are: `group`, `unknownFutureValue`, `roster`, `project`, `driveItem`, and `user`. You must use the `Prefer: include-unknown-enum-members` request header to get the following value in this [evolvable enum](/graph/best-practices-concept#handling-future-members-in-evolvable-enumerations): `roster`, `project`, `driveItem`, and `user`. Optional.|
34+
|type|plannerContainerType|The type of the resource that contains the plan. For supported types, see the previous table. Possible values are: `group`, `unknownFutureValue`, `roster`, `project`, `driveItem`, `user`, and `teamsChannel` . You must use the `Prefer: include-unknown-enum-members` request header to get the following value in this [evolvable enum](/graph/best-practices-concept#handling-future-members-in-evolvable-enumerations): `roster`, `project`, `driveItem`,`user`, and,`teamsChannel`. Optional.|
3435
|url|String|The full canonical URL of the container. Optional.|
3536

3637
## Relationships
3738
None.
3839

3940
## JSON representation
40-
The following example displays a JSON representation of a plan container.
41+
The following JSON representation shows the resource type.
4142

4243
<!-- {
4344
"blockType": "resource",
@@ -47,9 +48,9 @@ The following example displays a JSON representation of a plan container.
4748
``` json
4849
{
4950
"@odata.type": "#microsoft.graph.plannerPlanContainer",
50-
"url": "String",
5151
"containerId": "String",
52-
"type": "String"
52+
"type": "String",
53+
"url": "String"
5354
}
5455
```
5556

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

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -334,6 +334,12 @@ items:
334334
href: ../../resources/addlargegalleryviewoperation.md
335335
- name: Get large gallery view operation status
336336
href: ../../api/addlargegalleryviewoperation-get.md
337+
- name: Call events
338+
items:
339+
- name: Call event
340+
href: ../../resources/callevent.md
341+
- name: Emergency call event
342+
href: ../../resources/emergencycallevent.md
337343
- name: Call records
338344
items:
339345
- name: Overview

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

Lines changed: 7 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -2933,6 +2933,13 @@
29332933
"addLargeGalleryViewOperation"
29342934
]
29352935
},
2936+
{
2937+
"name": "Call events",
2938+
"resources": [
2939+
"microsoft.graph.callEvent",
2940+
"microsoft.graph.emergencyCallEvent"
2941+
]
2942+
},
29362943
{
29372944
"name": "Call records",
29382945
"overview": "../../resources/callrecords-api-overview.md",

‎changelog/Microsoft.Skype.Calling.json

Lines changed: 42 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,47 @@
11
{
22
"changelog": [
3+
{
4+
"ChangeList": [
5+
{
6+
"Id": "e554e67c-d299-46dd-9402-77b676082897",
7+
"ApiChange": "Enumeration",
8+
"ChangedApiName": "callEventType",
9+
"ChangeType": "Addition",
10+
"Description": "Added the **callEventType** enumeration type.",
11+
"Target": "callEventType"
12+
},
13+
{
14+
"Id": "e554e67c-d299-46dd-9402-77b676082897",
15+
"ApiChange": "Resource",
16+
"ChangedApiName": "emergencyCallerInfo",
17+
"ChangeType": "Addition",
18+
"Description": "Added the [emergencyCallerInfo](https://learn.microsoft.com/en-us/graph/api/resources/emergencyCallerInfo?view=graph-rest-beta) resource.",
19+
"Target": "emergencyCallerInfo"
20+
},
21+
{
22+
"Id": "e554e67c-d299-46dd-9402-77b676082897",
23+
"ApiChange": "Resource",
24+
"ChangedApiName": "callEvent",
25+
"ChangeType": "Addition",
26+
"Description": "Added the [callEvent](https://learn.microsoft.com/en-us/graph/api/resources/callEvent?view=graph-rest-beta) resource.",
27+
"Target": "callEvent"
28+
},
29+
{
30+
"Id": "e554e67c-d299-46dd-9402-77b676082897",
31+
"ApiChange": "Resource",
32+
"ChangedApiName": "emergencyCallEvent",
33+
"ChangeType": "Addition",
34+
"Description": "Added the [emergencyCallEvent](https://learn.microsoft.com/en-us/graph/api/resources/emergencyCallEvent?view=graph-rest-beta) resource.",
35+
"Target": "emergencyCallEvent"
36+
}
37+
],
38+
"Id": "e554e67c-d299-46dd-9402-77b676082897",
39+
"Cloud": "Prod",
40+
"Version": "beta",
41+
"CreatedDateTime": "2025-01-10T20:21:16.9977147Z",
42+
"WorkloadArea": "Cloud communications",
43+
"SubArea": "Call"
44+
},
345
{
446
"ChangeList": [
547
{

‎changelog/Microsoft.Tasks.json

Lines changed: 18 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,23 @@
11
{
22
"changelog": [
3+
{
4+
"ChangeList": [
5+
{
6+
"Id": "ac461ffd-f78b-4889-a030-1477634802db",
7+
"ApiChange": "Member",
8+
"ChangedApiName": "teamsChannel",
9+
"ChangeType": "Addition",
10+
"Description": "Added the `teamsChannel` member to the **plannerContainerType** enumeration.",
11+
"Target": "plannerContainerType"
12+
}
13+
],
14+
"Id": "ac461ffd-f78b-4889-a030-1477634802db",
15+
"Cloud": "Prod",
16+
"Version": "beta",
17+
"CreatedDateTime": "2025-01-12T20:25:44.9502669Z",
18+
"WorkloadArea": "Tasks and plans",
19+
"SubArea": ""
20+
},
321
{
422
"ChangeList": [
523
{

0 commit comments

Comments
 (0)