What Microsoft shipped
Microsoft's Customer Insights - Journeys release notes list "Automatically update emails with the latest content" as generally available in the August 2026 update, app release 1.2.2104.110. The same item appeared as a public preview in April 2026. Microsoft describes it as a way to remove manual work and the risk of sending emails with outdated content, because all emails using an updated block refresh automatically.
The roadmap entry (ID 577804) covers the web client in the Worldwide (Standard Multi-Tenant) cloud. It lists the feature as enabled automatically for admins, makers and marketers. Microsoft's roadmap notes that dates are estimates, and that entries may be removed once a feature is generally available.
One date discrepancy is worth knowing about. A Message Center notice (MC1386119), as mirrored by a third-party tracker, gave a general availability date of July 10, 2026. The release notes place GA in the August update. If you plan around a specific date, check what your own environment shows under its version settings.
Static vs dynamic blocks
A content block is reusable email content. It can hold text, images, links and buttons, and it can include layout. What matters is how an email uses the block:
- Static block: Microsoft's documentation says each email gets its own copy. Editing the original later does not change emails that already contain it. Use this for content that rarely changes, or when you want updates to apply only to new emails.
- Dynamic block: The email stores a reference instead of a copy. The content is fetched when the email is sent, so updates show up in every email that includes the block.
There are also two structural forms. Element blocks hold elements without a layout and take the shape of the column or section they are dropped into. Section blocks carry their own layout.
The use cases Microsoft describes
Microsoft's examples are legal boilerplate, business hours, a copyright year, and a "promotion of the week". The roadmap description adds a financial-services scenario. A company's footer carries a legal disclaimer plus a blurb with assets under management and recent awards. Maintaining that by hand across many campaigns is slow. It also risks one customer receiving two emails with conflicting information.
Dynamic blocks can include personalization. The roadmap says a block can use conditional content and dynamic text, such as showing only the awards relevant to a recipient's industry or financial level. Microsoft's documentation also gives an "Order" block as an example. It lists a customer's ordered items and works when the CRM relates the Contact table to the Order table.
Partner write-ups suggest similar scenarios: weekly promotional banners, legal footers revised by compliance teams, and contact details that change after a rebrand. That is partner interpretation, but it matches Microsoft's own examples.
Creating and editing a block
You can create a block in two ways:
- From the content block editor. Open the Content blocks item in the left navigation and select +New. Drag elements onto the canvas for an element block. Add layouts first and then content for a section block.
- From the email designer. Select an element or section and choose the Content block context menu item. A "Save as content block" dialog lets you create a new block or replace an existing one.
A block has these properties:
- Title, plus optional tags for searching.
- Type: static or dynamic.
- Ready to send: on by default. A Ready to send block can be inserted but cannot be edited until you switch it back to Draft. A Draft block can be edited but cannot be inserted.
- Protected: this applies only to static blocks, because dynamic blocks are always protected. A protected block cannot be changed inside an individual email.
To use a block, open an email in the designer and select the content block tab on the canvas toolbar. Blocks are labeled in the list. A lock icon means a protected static block. "Dynamic" means the block updates emails automatically. "Layout" means it is a section block.
To update a block, go to Assets > Content blocks and open it. If it is Ready to send, select Edit to move it to Draft. When you are done you can update the existing block or save the changes as a new block, which leaves the original untouched.
Risks and limitations
Live journeys can send mixed versions
This is the main operational caveat. Updating a dynamic block updates every email that uses it. If any of those emails are in a live journey, the new content is sent once the block is published as Ready to send. If the journey is actively sending to a large audience, different recipients might get different versions.
So a dynamic block does not guarantee that every recipient of one campaign sees identical content. For sensitive changes such as legal text, consider timing the publish around active sends.
Check the Settings pane before publishing
The Settings pane lists the emails and templates that use a block. For a dynamic block, it shows which emails will be updated automatically. Treat that list as your blast-radius check.
Deletion removes the block from emails
Deleting a dynamic block removes it from all emails that use it. A confirmation message tells you how many emails are affected and identifies them. Deleting a static block does not affect emails, since each has its own copy.
Testing gaps
Microsoft's documentation carries a notice that dynamic blocks do not appear in Preview & Test and are not rendered in Test send. It says they render correctly in sent emails in standard journeys. It also says a fix was expected to reach all regions by May 31, 2026. That date has passed, but the page I reviewed did not confirm the fix reached every region. Before you rely on a dynamic block for legal text, validate it in your own environment.
Link branching
Links inside dynamic blocks cannot be used for branching in journeys. Static blocks do not have this limitation. If a footer or banner link drives journey logic, use a static block or move that link outside the block.
Do you need to flip a feature switch?
The roadmap text says the feature is enabled automatically, but it also tells readers to turn on a "Dynamic content block" switch under Settings > Feature switches. These statements pull in different directions. Microsoft's general feature-switch page gives the path as Settings > Overview > Feature switches, then set the slider and select Save. Its published list of switches does not include a "Dynamic content block" entry.
My advice is to look at your environment. If the Content blocks area offers a dynamic type, you are set. If it does not, check Feature switches and your installed version before assuming anything is broken. Microsoft's release notes say updates are pushed automatically and tell administrators how to update manually.
Practical advice for marketing teams
- Put governed content in dynamic blocks: legal text, footers, business hours, and the copyright year.
- Keep one-off or campaign-specific content in static blocks.
- Use tags so authors can find the right block.
- Before publishing, review the Settings pane's affected-email list.
- Avoid publishing mid-send for large live audiences when version consistency matters.
- Use a sandbox or a small real send to verify rendering, given the documented Test send gap.
- Don't put branching links inside dynamic blocks.
The bottom line
Dynamic content blocks fix a long-standing problem. Without them, shared footer or disclaimer text gets pasted into dozens of emails and drifts out of sync. The trade-off is that one edit now touches many emails at once, including live ones. Teams that treat a dynamic block like production code, with review, timing and a blast-radius check, will get the consistency Microsoft promises.