Power Apps Personal Settings Refresh Targets December 2026: Classic Fallback Explained

For users, the practical question is straightforward: will changing a time zone or finding an email preference become easier? For support teams, there is another question worth answering before the interface arrives: what exactly does “switch to classic” switch back?

Microsoft’s documentation provides useful guidance on both points. It explains how to reach Personal settings, warns that some changes require two app refreshes, and describes the classic experience as a temporary troubleshooting fallback rather than a permanent destination.

What the roadmap says—and what it does not​

The November 13, 2026 roadmap entry identifies the following scope:

These fields need to be read together. “General Availability” in the release-ring field does not override “In development” in the status field. Likewise, “enabled by default” describes the intended user experience; it is not proof that every environment already has the update.

The listed version, 2611.4, is useful for tracking the announcement, but the entry does not provide an exact deployment day or a separate timetable for each government cloud. Organizations should not convert one December target into a promise of simultaneous worldwide availability. Microsoft explicitly says that roadmap dates are estimates and feature descriptions can change.

The announced change concerns how Personal settings is presented and navigated. It does not establish new permissions, revised data handling, or a replacement for every underlying preference. Nor does the Web designation establish availability in the native Power Apps mobile app.

That makes this a focused application-interface update, not a Windows servicing event. The useful preparation is user guidance and support readiness—not a hunt for a Windows KB.

An important wrinkle: documentation already calls it modern​

Microsoft Learn’s Personal settings documentation, updated October 30, 2026, already describes the modern experience as the default for model-driven apps. It also says the classic Set Personal Options experience is deprecated and will disappear in a future release.

That wording sits alongside a roadmap entry that still describes the modernization as in development for December. The available evidence does not explain precisely how those two publication states map to every deployed environment.

The responsible interpretation is to keep the claims separate: the roadmap supplies the planned release metadata, while Learn supplies the documented operating procedure and migration direction. Neither establishes that every tenant has the precise interface described by item 579899 today.

For an administrator preparing an internal notice, wording such as “Microsoft lists a Personal settings refresh for December” is therefore more defensible than “the new settings screen is now available to everyone.” A documentation page is useful operational evidence, but it is not a tenant-by-tenant deployment receipt.

How to open Personal settings​

For someone who already has access to a model-driven app, Microsoft documents this route:

1. Open the model-driven app.
2. In its upper-right corner, select Settings.
3. Select Personal settings.
4. Choose the relevant category and update the preference.

Microsoft notes that some changed settings might require refreshing the app twice before they take effect. If the modern settings experience itself causes a problem, select Switch to classic as a temporary workaround and report the issue to Microsoft Support.

A sensible verification step is to return to the part of the app affected by the preference. For a formatting change, inspect the displayed format; for an appearance preference, inspect the relevant screen. The goal is not merely to see a different value in a settings panel, but to confirm the intended result in use.

Avoid changing several unrelated options while troubleshooting. Changing one preference, checking the result, and recording any unexpected behavior gives support a clearer account than “I changed a few things and now it looks different.”

The documented refresh caveat is particularly useful here: an unchanged screen immediately after an edit is not, by itself, evidence that the preference failed to apply.

What users can adjust​

Personal settings covers considerably more than cosmetic preferences. Microsoft’s documentation groups options for navigation, regional display, calendars, synchronization, email, privacy, and language. These are existing documented capabilities, not a list of newly announced features in the December refresh.

Navigation, display, and regional preferences​

Under General, users can select a default home pane and tab. The default pane can follow the user’s role, and Microsoft explicitly notes that this home-pane setting does not apply when signing in through the Power Apps mobile app. General also includes time zone, default currency, high contrast, calling-code prefixing, and the default Advanced Find mode.

These options answer different questions. Time zone controls the regional time display; Formats controls the presentation of numbers, currency, time, and dates. Formats includes a preview and a Customize option. A support conversation about an unexpected date should therefore distinguish its presentation from its time-zone context before recommending a change.

There is also a practical performance consideration. Microsoft documents Rows Per Page values from 25 to 250, but recommends smaller values to help maximize grid performance. Showing more records at once is not automatically the better choice. That recommendation is existing settings guidance, not a performance improvement promised by the redesign.

For accessibility, the documented Enable high contrast option is relevant when someone uses high-contrast settings in their browser or operating system. A visual refresh should not be treated as a reason to overlook that established preference.

Appearance and calendar preferences​

The Appearance category covers visual preferences, including display density when the header and navigation refresh is enabled. That dependency matters: documenting an Appearance option does not establish that every app exposes it under every configuration.

Under Activities, users can choose their default calendar view and specify the start and end of their work hours. These settings deserve a place in onboarding guidance alongside regional preferences, particularly when helping someone make an unfamiliar app comfortable for daily use.

The editorial takeaway is modest but useful: better organization could reduce the effort required to find these controls. It does not prove that the controls themselves have gained new functionality.

Email and synchronization deserve deliberate changes​

Some preferences have consequences beyond how a screen looks. Microsoft documents synchronization filters for appointments, contacts, and tasks moving between Dynamics 365 and Outlook or Exchange, along with information about mapped fields and synchronization direction.

A cleaner settings panel is not a reason to experiment casually with those filters. For support teams, the relevant question is whether a user wants a different display or genuinely wants different information synchronized. Those are separate requests and should be handled separately.

The Email category includes automatic tracking choices, folder-tracking rules, automatic creation of leads or contacts from tracked messages, conversation display on the timeline, and access to mailbox details. It also includes an option allowing other Dynamics 365 users to send email on the account holder’s behalf. Microsoft warns that enabling this permits messages to be sent under that person’s name with or without their consent.

That warning deserves more attention than the new paintwork. Do not enable delegation or broaden email tracking merely to make an unfamiliar interface resemble an old screenshot. Establish the intended workflow first.

Personal settings also includes Email Templates and Email Signatures. Microsoft documents selecting New in the relevant category and entering the values for the template or signature; signature ownership can belong to a user or team. Those capabilities remain distinct from tracking and send-on-behalf preferences.

Missing options do not always indicate a fault​

Two documented configuration boundaries are especially useful for troubleshooting.

First, the Privacy tab is unavailable when an administrator has selected the privacy preference for the entire organization in System Settings. Where available, the user options govern whether error reports are sent to Microsoft automatically, only with permission, or not at all. A missing tab can therefore reflect organization policy rather than a broken modern interface.

Second, language preferences have administrative prerequisites. Base Language is not editable by the user. The interface and Help language options are separate, and additional languages require the administrator to install and enable the necessary language packs.

The practical response is to check configuration before declaring a regression. Repeatedly switching between modern and classic settings will not substitute for an organization-level language prerequisite or override a centrally selected privacy preference.

For an escalation, record the category involved, the expected option, the app being used, and what actually appears. Screenshots should avoid exposing unnecessary business or personal information. This is suggested support practice, not an additional requirement announced with the feature.

“Switch to classic” is not an app-wide rollback​

Microsoft’s Personal settings instructions explicitly describe Switch to classic as a temporary workaround for problems in modern Personal settings. They do not describe it as a way to restore the old appearance of the entire model-driven app.

That distinction matters because Microsoft separately documents an app-wide modernization program. Its New Look, covering forms, views, dashboards, dialogs, and controls, became mandatory by the April 2026 semiannual release. Microsoft says makers cannot switch a model-driven app back to the classic look.

A separate header and navigation refresh is described as generally available and opt-in, with availability beginning at build 2609.1 and potentially varying by region. That build belongs to the header refresh, not the Personal settings roadmap item’s 2611.4 metadata.

Support instructions should name the component being discussed rather than using “modern experience” as shorthand for everything. Otherwise, a perfectly valid Personal settings workaround can turn into an inaccurate promise about rolling back an entire application.

Also, deprecated does not mean already removed. Microsoft still documents the fallback, but its stated future removal makes it unsuitable as a permanent training strategy.

A proportionate preparation plan​

This announcement calls for targeted preparation rather than a major migration project. Based on the documented settings and fallback, a practical checklist is:

• Inventory existing help material. Identify instructions that rely on old Personal Options screenshots.
• Validate representative tasks. Check the preferences your users actually change, rather than treating every category as equally important.
• Separate configuration from interface faults. Check language prerequisites and organization-controlled privacy settings before escalating.
• Document the temporary fallback. Explain its limited scope and capture reproducible problems for support.
• Keep rollout language conditional. Communicate December as the roadmap target until availability is established in the relevant environment.

These are preparation recommendations, not newly announced Microsoft deployment requirements.

The potential benefit is straightforward: less time searching for ordinary preferences and fewer detours into an older interface. Whether the redesign delivers that benefit should be judged by completing real tasks, not by counting rounded corners.

For now, the most useful facts are the narrow scope, the planned December window, and the documented operational guidance. Users have a route to their preferences; support teams have a refresh caveat and temporary fallback; administrators have clear reasons not to confuse Personal settings with the wider model-driven app redesign. That is enough to prepare sensibly without turning a focused usability update into a platform overhaul.