Announcement List Governance, External Partners, and a Stale Offline Address Book
An engineering organization of 180 people needs an internal announcement list. Only six team leads may post; replies must not reach all 180; the list should be usable from Outlook. The same company needs to send a weekly status update to 35 external partner contacts without exposing their addresses to one another. An existing Microsoft 365 group, Eng-All, is already used for SharePoint document collaboration and is not suitable for announcements. HR reports that new hires can take up to two days to appear in the global address list, and several remote users see outdated entries in the offline address book. One team lead has been maintaining a 180-member contact group in her own Outlook, and it is frequently out of date.
1. Choose between a distribution list, a Microsoft 365 group, and a contact group for the 180-person announcement list, and explain the configuration for restricted posting and no reply-all.
Read the worked answer
Use a mail-enabled distribution group, not a contact group. A contact group is a personal Outlook item stored in one mailbox; it cannot be centrally managed, cannot restrict senders, and is exactly why the team lead's list is stale. A Microsoft 365 group brings a shared mailbox, SharePoint site, and conversation history that the announcement use case does not need. A distribution group is mail-only and can be restricted: set 'Only senders inside my organization' and add the six leads to the accepted-senders list, or use moderator approval. To prevent replies reaching all 180, a distribution group cannot suppress Reply All by itself; replies from non-approved senders will be rejected, which is noisy. If no replies at all is a hard requirement, send from a shared mailbox with the distribution group in BCC, or use transport rules to redirect replies to a monitored mailbox. Document that this is not a discussion list and keep membership in the group, not in a personal contact group.
2. How do you send the weekly update to 35 external partners without disclosing addresses, and why not a contact group?
Read the worked answer
Use BCC or a mail-enabled distribution group that contains the external contacts, with the sender's address in To. A contact group in Outlook is local to one profile; it is not centrally managed, not visible to colleagues, and not appropriate for a recurring company process. A distribution group of external contacts is manageable by IT and can be restricted to internal senders so partners cannot post to it. However, a distribution group still expands to individual recipients, and a Reply All by any partner would expose the list if the message was sent to the group. The safest pattern is a shared mailbox sending to the group in BCC, or a mail merge from a controlled contact list, with a clear 'do not reply all' instruction and a monitored reply address. If partners must collaborate with each other, consider a Microsoft 365 group with guests, but that intentionally discloses membership and requires guest governance. For a one-way update, BCC is the right default.
3. New hires take up to two days to appear, and remote users see stale offline address book entries. What is happening and what do you check?
Read the worked answer
In cached Exchange Mode, Outlook resolves names against the offline address book, which is generated on Exchange and downloaded periodically; it is not a live global address list lookup. A new hire can be mailbox-enabled immediately and still be missing from the offline address book until the next generation and client download. Check first that the user is mailbox-enabled and not hidden from address lists; then trigger an offline address book update on the server and have the client choose Send/Receive > Download Address Book with full details. Remote users on slow links may have stale files; confirm the download completed and the version changed. For immediate lookup, users can use the global address list while online or clear the offline cache. Do not 'fix' this by recreating the user. Set expectations that propagation is typically up to 24 to 48 hours, and monitor the generation schedule.