Outlook for iOS and Android: Send button relocated to reduce accidental sends [MC1134176]

Message ID: MC1134176

Introduction

To help reduce accidental message sends, Outlook mobile is updating the placement of the Send button in the compose view. The button will move from the bottom toolbar to the header area, placing it in a less crowded location. This change supports a more intentional and error-free messaging experience for mobile users by minimizing the likelihood of accidental taps.

This message is associated with Microsoft 365 Roadmap ID 499900.

When this will happen

General Availability (Worldwide, GCC, GCC High, and DoD): We will begin rolling out in early September 2025 and expect to complete by early March 2026.

How this will affect your organization

Once this change is deployed, users on Outlook mobile clients (Android and iOS) will see the Send button relocated to the top of the compose view. This update is designed to reduce accidental taps and improve usability. The feature will be enabled by default.

The following screenshots illustrate the updated Send button placement in the compose view on Outlook mobile.

Image 1 – New Send button placement in Outlook for iOS – full compose view:

 

Image 2 – New Send button placement in Outlook for iOS – small compose view: 

Image 3 – New Send button placement in Outlook for Android – full compose view: 

 

This change does not affect Outlook on the web or desktop clients.

• Add-ins and customizations: This change does not affect existing add-ins or customizations in the compose view.
• Accessibility tools and keyboard shortcuts: There will be no impact.
• Consistency: The new placement is consistent across screen sizes and supported browsers.

What you can do to prepare

No admin action is required.

We recommend notifying your users about this change and updating any relevant training materials or documentation to reflect the new button placement.

If applicable, test any custom add-ins or UI extensions in the compose view to ensure compatibility, although no known impact is expected.

Compliance considerations

No compliance considerations identified, review as appropriate for your organization.

Source: Microsoft

Latest Posts