Microsoft 365 updates: Teams, Outlook and Entra changes

Key insights

• Teams is adding guest-invitation reporting and context-aware phishing warnings, with rollout windows described as November and December.
• Teams admins can customize extensions blocked by weaponizable file protection.
• Outlook alias sending is generally available but must be enabled through the Exchange Admin Center or PowerShell.
• Microsoft Entra agent blueprints are enabled for default users from November 4 unless admins turn off the setting.
• Conditional Access policy plans and inactive-agent lifecycle policies are described as public preview.

Microsoft 365 is adding security, administration and productivity changes across Teams, Outlook, Entra and Copilot. These updates matter to Microsoft 365 administrators and users who manage collaboration, identity settings or day-to-day work in the suite. Nick Ross [MVP] (T-Minus365) summarizes and demonstrates selected changes in a YouTube video.

What's new

The update overview covers changes in several products rather than one single feature. Teams is adding tools to report suspicious guest invitations, warn users about contextually suspicious messages, and manage blocked file extensions. Other Teams changes include side conversations in meeting chats, simultaneous screen sharing by two presenters, and direct file sharing in external chats.

For Outlook and Exchange, users can send from an email alias after an administrator enables the capability. New Outlook for Windows is also adding an All accounts view, while an inbox-rule option can reply to incoming messages with a template. Teams Phone voicemail email settings are gaining more control over message delivery and sender details.

In Microsoft Entra, the overview highlights Conditional Access policy plans, a setting for who can create agent blueprints, and lifecycle policies for inactive agents. Copilot updates mentioned include Copilot Code in Frontier, Projects, a cost-management Graph API, work-data personalization for memory, and usage-based billing in more Microsoft 365 apps.

Who it is for and what you need

Microsoft 365 administrators should focus on settings that affect security or access: Teams’ blocked file extensions, Outlook alias sending, and Microsoft Entra agent creation. Entra policy plans and inactive-agent lifecycle policies are identified in the demonstration as public preview, so the presenter says they are available to try in some tenants; the source does not specify eligibility details.

Some changes are user-facing, including meeting side conversations, dual screen sharing, the Outlook All accounts view and alias sending. The overview says alias sending requires configuration in the Exchange Admin Center or through PowerShell; it does not give the exact steps. It describes Teams Phone Agent as rolling out to general availability and says a Copilot license is needed to use it.

The speaker gives rollout windows for several announcements, but those are estimates presented in the video, not guarantees for every tenant. The material does not establish regional availability, other licensing requirements, or whether every feature is enabled by default. Confirm current status and prerequisites in your own tenant before changing policy or communicating a rollout date.

How it works

Several updates require administrator attention, while others change how users work in Teams and Outlook. For the configuration details that the source provides, the practical paths are:

1. To enable sending from an Outlook email alias, use the Exchange Admin Center or PowerShell. The video says this is not enabled by default and identifies the capability as generally available.
2. To limit who can create Microsoft Entra agent blueprints, review the relevant user setting in the Microsoft portal. The speaker says default users will be able to create blueprints from November 4 unless an administrator turns the setting off.
3. To adjust Teams’ blocked file extensions, customize the extension list in the weaponizable file protection service. The feature is described as on by default, with administrators able to add or remove extensions.
4. To try Conditional Access policy plans or inactive-agent lifecycle policies, look for the preview features in the Microsoft portal. The video does not provide a detailed click path or a complete configuration walkthrough.

For Teams users, the new side conversation is intended for meeting participants who need to talk privately without putting the exchange in the meeting chat. Simultaneous screen sharing lets two presenters show their screens at once, which the presenter identifies as useful for comparing content or troubleshooting.

External chat file sharing changes an earlier restriction: the speaker says that direct sharing through the paperclip or drag-and-drop was not previously available, and that an earlier workaround used PowerShell. The described change is to make the capability available by default, although the rollout timing is still listed as undetermined.

Limitations and open questions

The video is a monthly selection, not a complete change log, and its transcript ends partway through the Copilot updates. It therefore does not provide a full account of all Microsoft 365 changes or the rest of the Copilot billing announcement. The research notes supplied alongside the transcript mention other features, but no corresponding official Microsoft URLs are included in the allowed source list, so those claims are not included here.

Several rollout windows are stated in the demonstration: for example, Teams guest-invitation reporting is described as arriving in early November, while direct external-chat file sharing has no official date. These are the speaker’s summaries of announcements, and the material does not independently verify rollout status. Check the Microsoft 365 admin center or product documentation for current tenant-specific information before relying on a date.

The video also includes the presenter’s personal opinions about whether organizations should deploy Teams Phone Agent and whether admins should disable agent creation for default users. Those are recommendations, not product requirements. Teams Phone Agent’s capabilities and availability are described, but the source does not provide detailed setup steps, licensing beyond the Copilot license mention, or a complete security assessment.

Sources

• Nick Ross’s Microsoft 365 updates overview

Frequently asked questions

How do I enable sending from an Outlook email alias?

The source says to configure it in the Exchange Admin Center or with PowerShell. It does not give the exact steps, and says the feature is not enabled by default.

Can Microsoft Entra admins control who creates agent blueprints?

Yes. The video points to a user setting in the Microsoft portal and says default users will be able to create blueprints from November 4 unless admins turn the setting off.

Are Conditional Access policy plans generally available?

The source describes them as a public preview available to try in some tenants. It does not provide a general-availability date.

What does Teams Phone Agent require?

The video says a Copilot license is required and describes the agent as rolling out to general availability. It does not specify additional prerequisites.