Microsoft has added a setting that can make selected custom organizational attributes available through its employee-profile services. For a credit union using the Organizational Data Service, that creates a decision for HR and IT before enabling another flow of workforce information.

The November 17 release notes say the capability is off by default and requires administrator action. Selected custom attributes shared to Microsoft 365 experiences become visible to users across the tenant, including guests. Organizations that do not use the service, or leave the capability disabled, experience no change. Microsoft also describes a gradual rollout; the announcement does not establish availability in a particular credit union’s tenant.

The company’s data-distribution documentation explains that employee-profile information supplies context to services including profile cards, search, Copilot and agents. Choosing which applications receive data is not the same decision as deciding that a field belongs in an employee-facing profile.

A useful field can still have the wrong audience

Consider a hypothetical internal label used to plan a colleague’s training. A course-completion date might help another employee find someone with relevant expertise. A provisional assessment or a manager’s development note has a different purpose. Putting both under a broad skills label does not make their audiences interchangeable.

Before enabling the setting, HR can identify the meaning and owner of each proposed attribute while IT checks its destination and visibility. Use a non-sensitive test record to inspect the ordinary employee and guest views, and confirm how corrections reach the profile after the source record changes. These are proposed acceptance checks, not results from a CUAI tenant test.

The immediate choice is whether the information should be shared at all. Better colleague discovery is useful only when the profile shows information that is suitable for the people who can see it.