Starting in July 2026, Microsoft Teams will begin displaying the names of designated administrative assistants directly inside the app’s Organization view. The rollout, confirmed on the Microsoft 365 Roadmap, brings the long‑available “Assistant” field from Exchange and Entra ID into profile cards and the Org Explorer, giving colleagues immediate context on who handles scheduling, email, and other administrative tasks for a given person.

For years, the Assistant attribute has been a quiet but critical piece of directory data. In on‑premises Active Directory, it’s often filled during user creation; after synchronization, it lives in Entra ID and powers the “Request a Meeting” workflow in Outlook. Now Microsoft is plugging that same information into the collaboration hub that millions of workers use every day. The result: a subtle but meaningful change to how people find and connect with the assistants who keep large teams running smoothly.

The Assistant field – a hidden directory gem

Before understanding what’s coming to Teams, it helps to know where the data comes from. The Assistant field is a single‑valued text attribute in Entra ID (and on‑prem Active Directory). It typically stores the display name or alias of the person who acts as an administrative assistant for the user. In some organizations, it holds a username or even a group email; in others, it’s left empty. When populated, Outlook uses it to offer an “Assistant” tab in meeting invitations, allowing attendees to copy the assistant on meeting requests or route scheduling to them.

This attribute is exposed in the Microsoft 365 admin center under user properties, but few admins manage it proactively. Many organizations rely on HR systems to push the value into AD, and it eventually syncs to the cloud. Despite its low profile, the field is a linchpin for executive scheduling and has been a staple of Exchange for decades. By surfacing it in Teams, Microsoft is extending the assistant concept beyond email into the real‑time collaboration layer.

Where exactly will the assistant appear in Teams?

According to the roadmap item, the Assistant field will show up in two key places:

  • Profile cards: When you hover over a person’s name or click their picture anywhere in Teams, the profile card will display the assistant’s name, just as it already shows job title, department, and manager.
  • Organization view (Org Explorer): In the full Org Explorer, the assistant will be listed on the target user’s node, perhaps as a sub‑node or an additional detail. This makes it easy to see the entire reporting structure and then immediately spot who supports a particular leader.

The feature will be available on Teams for desktop, Mac, and the web. Mobile platforms are not mentioned in the initial scope, though a broader rollout often follows. The assistant’s name will be clickable, enabling users to open a chat or view the assistant’s own profile card, further streamlining communication.

Why this matters for everyday collaboration

In large enterprises, knowing who an executive’s assistant is can be a daily puzzle. Perhaps you need to schedule a meeting with a VP but the VP’s calendar is managed by someone else. Or you’re sending an urgent message and want to ensure the right support person is looped in. Currently, that knowledge often depends on institutional memory or a separate address book. With the assistant field inside Teams, this information becomes visible at a glance, right within the tool where the conversation or meeting is happening.

This also simplifies a frequent ritual: the back‑and‑forth of “Who handles so‑and‑so’s calendar?” In Outlook, the assistant information is sometimes visible on the Scheduling Assistant tab or in contact cards, but Teams has lacked that context. Adding it directly to profile cards means you can check during a chat, while viewing a channel post, or while planning a meeting in the Teams calendar. It reduces friction and keeps users in the flow of work.

Technical prerequisites and admin controls

For the assistant data to appear, the field must be populated in Entra ID. Administrators can verify this in the Microsoft Entra admin center by navigating to a user’s profile and checking the “Assistant” entry under the “Job info” tab. If it’s empty, no information will show in Teams. Organizations that never filled this attribute will need to start doing so to benefit from the feature.

For hybrid environments, the value typically comes from on‑prem Active Directory. Admins should ensure the attribute is replicated correctly via Azure AD Connect (or the newer cloud sync). The field is a directory extension, not a custom attribute, so it has a fixed name and is supported out of the box. There is no additional licensing requirement beyond a standard Microsoft 365 subscription that includes Teams.

The feature itself will be enabled by default, with no way for individual users to hide their own assistant field if an admin has set it. However, organizations can request that certain profiles not show the assistant for privacy reasons – such a request would likely be handled through the existing Microsoft 365 feedback channels or by tagging the attribute as sensitive. At launch, the only control may be removing the data at its source.

Rollout timeline and availability

Microsoft’s message is consistent: general availability is July 2026. Rollouts like this typically follow a staged approach: first, targeted release tenants in early July, then standard release across the following weeks. The feature is expected in the standard, GCC, and GCC High environments, though specific dates for government clouds can lag by a few months. Teams for Education subscribers will also receive it, though the assistant field is less common in academic settings.

Because the feature draws on existing directory data, there is no new workload to install. Once the rollout reaches a tenant, the assistant information will simply appear where the field is filled. Admins and user‑adoption teams should plan communications ahead of time so that employees understand where the data comes from and how to interpret it.

Potential pitfalls and organizational considerations

The main risk is inaccurate or outdated data. If an assistant changes roles and the AD field isn’t updated, Teams will show the wrong person – leading to misdirected meeting requests and confusion. This places a premium on good HR feed hygiene and regular audits of the individual attribute. Some organizations may want to use this rollout as an opportunity to review their directory accuracy.

Privacy is another consideration. While an assistant’s name is usually benign, some employees might feel uncomfortable having their support relationship broadcast across the company. Microsoft has historically taken a broad approach to directory visibility, with the assumption that most enterprise data is meant to be shared within the organization. Organizations with strict privacy cultures should evaluate whether the benefit outweighs any potential employee pushback.

A subtler concern is that the assistant field exposes a job title or role that might not align with how the assistant sees themselves. Many administrative professionals have titles like “Executive Assistant” or “Office Coordinator”; the field simply says “Assistant,” which could feel reductive. Communications around the feature should highlight that this is a technical name tied to a longstanding directory field, not a value judgment.

The bigger picture: Directory‑first collaboration

The addition of the assistant field is part of a broader trend in Microsoft 365: making directory data more actionable across all apps. In recent years, Teams profile cards have gained Org Chart, LinkedIn integration, and shared files. The assistant field continues that trajectory by pulling in a piece of data that was previously confined to Outlook and Exchange. It reflects Microsoft’s recognition that the organization’s structure isn’t just a static diagram – it’s a living network of roles that influence how work gets done.

This also aligns with the evolution of Microsoft’s directory itself. As Entra ID absorbs more identity attributes – from skills and interests to project roles – more of that data will appear in collaborative surfaces like Teams, Viva, and the Office suite. The assistant field is a low‑hanging fruit today; tomorrow, we might see fields like “Cost Center” or “Team Lead” appearing in profile cards. The ultimate goal is a richer, context‑aware collaboration experience that reduces the need to switch between apps.

Steps IT admins should take now

If your organization wants to be ready for the July 2026 debut, there are a few proactive moves:

  • Populate the Assistant attribute. Work with HR and directory teams to ensure this field is filled for assistants and the people they support. Automated provisioning from HR systems is the most sustainable approach.
  • Audit existing data. Use the Microsoft Graph API or Entra ID’s user listing to export all users and check the Assistant field for accuracy. Fix any obsolete entries.
  • Communicate the change. Prepare a short internal announcement explaining what the new profile data means and how it will appear. Emphasize that the information already exists in Outlook; Teams is just making it more visible.
  • Update internal directories. If your company relies on SharePoint lists or third‑party phone books, align them with the same single source of truth to avoid contradictions.
  • Test the user experience. Once the rollout hits your tenant, open a few executive profile cards and verify the assistant is correctly displayed and clickable. Provide feedback through the Microsoft 365 admin center if something looks off.

What to expect after launch

After the feature lands, the assistant field will likely evolve. Microsoft may add presence indicators – showing whether the assistant is online, away, or in a meeting. There could be a quick action to “Schedule with assistant” directly from the profile card, mimicking Outlook’s behavior but inside Teams. The company might also integrate the field into its Copilot for Microsoft 365 experience, so that natural language prompts like “Find John’s assistant” return the correct person.

For now, the July 2026 date gives organizations ample time to prepare. The change itself is small – just one extra line on a profile card – but it represents a better connected view of how people work together. When everyone knows who to call, meetings get scheduled faster, messages reach the right inbox, and the daily friction of corporate communication eases just a little. That’s a win worth waiting for.