# Legacy Outlook Email Status Update via HTTP Call **Last reviewed:** September 30, 2026 This page is retained as a legacy integration reference for environments that still update Outlook email status through an HTTP call. ## What changed in this article - Marked the Outlook HTTP-call procedure as legacy and integration-specific because Microsoft authentication and Graph/API behavior can change. - Added checks for OAuth/token handling, endpoint ownership, least-privilege permissions, response validation, and audit logging. - Added guidance to avoid hard-coded credentials and to confirm whether Microsoft Graph or a maintained integration should replace this approach. ## Validation workflow 1. Confirm the customer still needs this legacy HTTP-call workflow and identify the supported endpoint. 2. Validate authentication, permission scope, request body, expected status code, and failure response in a controlled test. 3. Document token storage and audit requirements before using the workflow in shared automation. **Review note:** This page now warns that Outlook status changes should use maintained Microsoft/API practices where available. --- Last updated: September 30, 2026 If you have feedback on this topic, contact .