[MS] Deprecation of MS-APP-ACTS-AS header in Shifts Management Microsoft Graph APIs - devamazonaws.blogspot.com

In app-only access scenarios, Shifts Management Graph APIs previously required the MS-APP-ACTS-AS: userId header to indicate the user on whose behalf the application was acting. However, this conflicted with the Microsoft Graph permission model where there is no signed-in user for app-only access scenarios. To align Shifts Graph APIs with this model, the MS-APP-ACTS-AS header has now been deprecated.

What Action You Need to Take

If you don’t send the header today

There is no impact. No changes are necessary.

If you send the header today

1. Please remove the header. Example: Old: GET /teams/{teamId}/schedule/shifts MS-APP-ACTS-AS: d56f3e8a-2b0f-42b1-88b9-e2dbd12a34d2 New: GET /teams/{teamId}/schedule/shifts 2. For offerShiftRequest, openShiftsChangeRequest, swapShiftsChangeRequest, timeOffRequest, or timeCard, you may need to switch to a new API or add an additional property in the request body. Please see the instructions below. ScheduleChangeRequest (offerShiftRequest, openShiftsChangeRequest, swapShiftsChangeRequest, timeOffRequest) Approve a ScheduleChangeRequest
  • If you are using /approve API with application permissions, please use /approveForUser instead.
  • Eventually, /approve will only support delegated permissions
Old API New API
teams/{teamId}/schedule/offerShiftRequests/{requestId}/approve teams/{teamId}/schedule/offerShiftRequests/{requestId}/approveForUser
teams/{teamId}/schedule/openShiftsChangeRequests/{requestId}/approve teams/{teamId}/schedule/openShiftsChangeRequests/{requestId}/approveForUser
teams/{teamId}/schedule/swapShiftsChangeRequests/{requestId}/approve teams/{teamId}/schedule/swapShiftsChangeRequests/{requestId}/approveForUser
teams/{teamId}/schedule/timeOffRequests/{requestId}/approve teams/{teamId}/schedule/timeOffRequests/{requestId}/approveForUser
Example Old: POST /teams/{teamId}/schedule/timeOffRequests/{requestId}/approve MS-APP-ACTS-AS: d56f3e8a-2b0f-42b1-88b9-e2dbd12a34d2 Content-type: application/json { "message": "approved" } New: POST /teams/{teamId}/schedule/timeOffRequests/{requestId}/approveForUser Content-Type: application/json { "message": "approved", “userId”: "d56f3e8a-2b0f-42b1-88b9-e2dbd12a34d2" }

Decline a ScheduleChangeRequest

  • If you are using /decline API with application permissions, please use /declineForUser instead.
  • Eventually, /decline will only support delegated permissions
Old API New API
teams/{teamId}/schedule/offerShiftRequests/{requestId}/decline teams/{teamId}/schedule/offerShiftRequests/{requestId}/declineForUser
teams/{teamId}/schedule/openShiftsChangeRequests/{requestId}/decline teams/{teamId}/schedule/openShiftsChangeRequests/{requestId}/declineForUser
teams/{teamId}/schedule/swapShiftsChangeRequests/{requestId}/decline teams/{teamId}/schedule/swapShiftsChangeRequests/{requestId}/declineForUser
teams/{teamId}/schedule/timeOffRequests/{requestId}/decline teams/{teamId}/schedule/timeOffRequests/{requestId}/declineForUser
Example Old: POST /teams/{teamId}/schedule/timeOffRequests/{requestId}/decline MS-APP-ACTS-AS: d56f3e8a-2b0f-42b1-88b9-e2dbd12a34d2 Content-type: application/json { "message": "declined" } New: POST /teams/{teamId}/schedule/timeOffRequests/{requestId}/declineForUser Content-Type: application/json { "message": "declined", “userId”: "d56f3e8a-2b0f-42b1-88b9-e2dbd12a34d2" }

Create a TimeOffRequest

  • POST teams/{teamId}/schedule/timeOffRequests
  • Previously, senderUserId was an optional property as the value provided by MS-APP-ACTS-AS was used as the sender user ID. Since MS-APP-ACTS-AS is deprecated, please provide the sender user ID through senderUserId property.
  • Example
Old: POST teams/{teamId}/schedule/timeOffRequests MS-APP-ACTS-AS: d56f3e8a-2b0f-42b1-88b9-e2dbd12a34d2 Content-type: application/json { "timeOffReasonId": "TOR_08c42f26-9b83-492c-bf52-f3609eb083e3", "startDateTime": "2025-05-26T07:00:00Z", "endDateTime": "2025-05-27T07:00:00Z" } New: POST teams/{teamId}/schedule/timeOffRequests Content-type: application/json { "timeOffReasonId": "TOR_08c42f26-9b83-492c-bf52-f3609eb083e3", "startDateTime": "2025-05-26T07:00:00Z", "endDateTime": "2025-05-27T07:00:00Z", "senderUserId": "3f2504e0-4f89-11d3-9a0c-0305e82c3301" }

Create an OpenShiftsChangeRequest

  • POST /teams/{teamId}/schedule/openShiftChangeRequests
  • Previously, senderUserId was an optional property as the value provided by MS-APP-ACTS-AS was used as the sender user ID. Since MS-APP-ACTS-AS is deprecated, please provide the sender user ID through senderUserId property.
Example Old POST teams/{teamId}/schedule/openShiftChangeRequests MS-APP-ACTS-AS: d56f3e8a-2b0f-42b1-88b9-e2dbd12a34d2 Content-type: application/json { "senderMessage": "Can I take this shift?", "openShiftId": "577b75d2-a927-48c0-a5d1-dc984894e7b8" } New POST teams/{teamId}/schedule/openShiftChangeRequests Content-type: application/json { "senderMessage": "Can I take this shift?", "openShiftId": "577b75d2-a927-48c0-a5d1-dc984894e7b8", "senderUserId": "d56f3e8a-2b0f-42b1-88b9-e2dbd12a34d2" }

TimeCard

Confirm a TimeCard

  • Please use /confirmForUser instead of /confirm.
Old API New API
teams/{teamId}/schedule/timeCards/{timeCardId}/confirm teams/{teamId}/schedule/timeCards/{timeCardId}/confirmForUser
Example: Old POST teams/{teamId}/schedule/timeCards/{timeCardId}/confirm MS-APP-ACTS-AS: d56f3e8a-2b0f-42b1-88b9-e2dbd12a34d2 New POST teams/{teamId}/schedule/timeCards/{timeCardId}/confirmForUser Content-Type: application/json { “userId”: "d56f3e8a-2b0f-42b1-88b9-e2dbd12a34d2" }

Clock in a TimeCard

  • POST teams/{teamId}/schedule/timeCards/clockIn
  • Previously, onBehalfOfUserId was an optional property as the value provided by MS-APP-ACTS-AS was used as the ID of the user that is clocking in. Since MS-APP-ACTS-AS is deprecated, please provide the ID of the user that is clocking in through onBehalfOfUserId property.
  • Example:
Old POST teams/{teamId}/schedule/timeCards/clockIn MS-APP-ACTS-AS: d56f3e8a-2b0f-42b1-88b9-e2dbd12a34d2 New POST teams/{teamId}/schedule/timeCards/clockIn Content-type: application/json { "onBehalfOfUserId": "3f29c8e7-7a41-4d8e-99d6-2b1f76c9421e" }

Create a TimeCard

  • POST /teams/{teamId}/schedule/timeCards
  • Previously, userId was an optional property as the value provided by MS-APP-ACTS-AS was used as the ID of the owner of the timeCard. Since MS-APP-ACTS-AS is deprecated, please provide the ID of the timeCard owner through userId property.
Example Old POST /teams/{teamId}/schedule/timeCards MS-APP-ACTS-AS: d56f3e8a-2b0f-42b1-88b9-e2dbd12a34d2 Content-Type: application/json { "clockInEvent": { "dateTime": "2025-01-07T21:00:00.000Z", "isAtApprovedLocation": true }, "clockOutEvent": { "dateTime": "2025-01-07T21:30:00.000Z", "isAtApprovedLocation": true } } New POST /teams/{teamId}/schedule/timeCards Content-Type: application/json { “userId”: “d56f3e8a-2b0f-42b1-88b9-e2dbd12a34d2”, "clockInEvent": { "dateTime": "2025-01-07T21:00:00.000Z", "isAtApprovedLocation": true }, "clockOutEvent": { "dateTime": "2025-01-07T21:30:00.000Z", "isAtApprovedLocation": true } }  
Post Updated on June 23, 2025 at 04:30PM
Thanks for reading
from devamazonaws.blogspot.com

Comments

Post a Comment

Popular posts from this blog

Scenarios capability now generally available for Amazon Q in QuickSight - devamazonaws.blogspot.com

Today, AWS announces the general availability of the scenarios capability of Amazon Q in QuickSight. Amazon Q guides you through data analysis by uncovering hidden trends, making recommendations for your business, and intelligently suggesting next steps for deeper exploration—all in response to natural language interactions. Now anyone can explore past trends, forecast future scenarios, and model solutions without needing specialized skill, analyst support, or manual manipulation of data in spreadsheets. With its intuitive interface and step-by-step guidance, the scenarios capability of Amazon Q in QuickSight helps users perform complex data analysis up to 10x faster than spreadsheets. Whether you're optimizing marketing budgets, streamlining supply chains, or analyzing investments, Amazon Q makes advanced data analysis accessible so you can make data-driven decisions across your organization. This capability is accessible from any Amazon QuickSight dashboard, so you can move seam...
Read more

Research and Engineering Studio on AWS Version 2024.08 now available - devamazonaws.blogspot.com

Today we’re excited to announce Research and Engineering Studio (RES) on AWS Version 2024.08. This release adds new features such as Amazon S3 bucket mountpoints for Linux, allows creation of custom user roles and permission profiles, and offers the ability to adjust the list of Amazon EC2 instances available to launch as virtual desktops. Amazon S3 mountpoints allow Linux desktops to access S3 buckets as a file system. Amazon S3 buckets are created using the AWS Console or AWS CLI and onboarded to RES by administrators using the S3 Buckets page in the web portal. You can mount buckets in either Read Only or Read/Write mode. Read/Write buckets have an optional setting to restrict data access by project, or both project and user. RES can also mount S3 buckets from other AWS accounts with the proper permissions. Custom permission profiles allow administrators to create unique permissions and assign them to users or groups. Start by modifying the default Project Member and Project Ow...
Read more

Amazon EC2 C6id instances are now available in AWS Europe (Paris) region - devamazonaws.blogspot.com

Starting today, Amazon Elastic Compute Cloud (Amazon EC2) C6id instances are available in Europe (Paris) Region. These instances are powered by 3rd generation Intel Xeon Scalable Ice Lake processors with an all-core turbo frequency of 3.5 GHz and up to 7.6 TB of local NVMe-based SSD block-level storage. C6id instances are built on AWS Nitro System , a combination of dedicated hardware and lightweight hypervisor, which delivers practically all of the compute and memory resources of the host hardware to your instances for better overall performance and security. Customers can take advantage of access to high-speed, low-latency local storage to scale performance of applications such data logging, distributed web-scale in-memory caches, in-memory databases, and real-time big data analytics. These instances are generally available today in the US West (Oregon), US East (Ohio, N. Virginia), Canada (Central), Canada West (Calgary), AWS GovCloud (US-West), Mexico (Central), South America (...
Read more