Teams Events App / Plug-in, targeting events vs registration

You need registration and attendance tracking while showing each event only to its language or time-zone audience. Microsoft’s current Teams documentation treats attendee access, registration, and event policies as separate controls; it does not document an Events-app setting that combines registration with audience targeting or subdivides one tenant. For now, create one event instance per audience, choose the narrowest supported attendance scope, and distribute each registration link through the matching security group, team, or targeted message. Test with one user from every audience before publishing, including notifications and calendar behavior. Additional teams or Microsoft 365 groups can organize delivery, but they do not create isolated tenant partitions. If separate administrative or data boundaries are mandatory, treat that as a tenant architecture decision. Microsoft has not committed publicly to this combination, so submit feedback and monitor the Microsoft 365 roadmap and Message center rather than planning around an unannounced change.