
Self-service Power Pages ownership transfer has no undo
Power Pages site owners can now be reassigned without a support case, and Microsoft's own documentation says the transfer cannot be automatically undone.
Topic coverage
Source-linked reporting and practical patterns organized around a shared enterprise applications question.

Power Pages site owners can now be reassigned without a support case, and Microsoft's own documentation says the transfer cannot be automatically undone.

A correction. We said no version-pinned Brazil documentation link existed. One does, and this is the URL form that produces it.

ServiceNow's Brazil release notes are live and dated, with a documented September 24 Early Availability date and roughly 90 product areas changed.

Microsoft now provisions and renews SSL and TLS certificates for Power Pages custom domains, but the option does not appear when CDN or WAF is enabled.

Salesforce says requests stalled on an internal login service. Authentication is the dependency most continuity plans never wrote down.

Workday 2026R2 reached production on a Saturday. The automatic and optional change split is Monday's problem, and Agent Passport deserves harder questions.

Workday is a Leader in the first Gartner workforce management quadrant. A first edition changes how much weight that position can carry in a shortlist.

Microsoft put more than 200 auto-generated API commands into the Power Platform CLI preview. Governance and licensing are now a script away.

Oracle September update shipped 673 patches, but the number that matters is how many are reachable without a login, and Oracle already named where that risk concentrates.

Microsoft's AI at Work roadmap, Message Center, and Learn each answer a different planning question. Here is which channel each decision belongs to.

Microsoft's always-on AI at Work roadmap removes the wave date that used to force a review. Someone in your tenant now has to own that date.

Microsoft's August 25 post keeps public roadmap items and tenant change notices in separate channels. Someone on your team has to join them.

Microsoft retires Release Planner on November 15, 2026. What admins and architects should export, rebookmark, and reschedule before that date.

Seasonal releases mostly add capability. Release Updates change platform behaviour your configuration already depends on, and enforcement arrives either way.

Agents can build the field, the flow and the report. What they cannot do is know why your configuration looks the way it does, or which request to refuse.

Release waves are gone, so the release channel on each environment now decides when your users meet change. Most estates have never deliberately set it.

Winter '27 lands October 12, the Release Planner retires November 15, Brazil is arriving and 2026R2 is already live. Six vendors, one team calendar.

Oracle publishes no global NetSuite release dates, and a Release Preview account takes 5 to 7 days to build and is purged after 14 days without a login.

Winter '27 is generally available October 12, 2026. If your test sandbox was never on a preview instance, refreshing it is the only way onto one.

ServiceNow supports only the current and previous release family, so falling two behind turns your upgrade into one ServiceNow schedules for you.

Microsoft is retiring the twice-yearly release wave model. Release plans stop publishing in September 2026 and the Release Planner retires by November 15.

Workday ships two feature releases a year plus weekly service updates, and nearly all of it arrives disabled, so the real risk is what nobody turns on.

You cannot decline a Fusion Cloud quarterly update forever, so the work is preparation. Who reads the readiness material, and what a regression pack should cover.

A certification is worth the week when a partner badge, a procurement filter or a thin CV depends on it. For a proven in-house admin, rarely.

S/4HANA support packs arrive on a plan and BTP services do not. How to split the reading, triage notes, and keep a record that lasts.

A concrete method for sorting Power Platform's twice-yearly release waves and daily message center posts from noise into action.

An unused seat still gets billed. Cross usage logs against the assignment list, flag the quiet accounts, and reclaim seats before renewal locks the price in.

A ledger of what you skipped and a five-line summary do more for ServiceNow release review than reading the whole document ever will.

A release note is sixty decisions someone else already made. Three questions and a one-line record find the four that need an owner and a date.

A green run history hides the cleanup that follows a bad Power Automate run. Name the recovery owner and measure time to a resolved outcome.

Content assignment decides what a user sees, authorisation decides what runs, and the two drift apart unless you design roles around the job.

Subsidiaries should track legal entity structure, not divisions. Settle the hierarchy, base currency and access design before the first transaction posts.

A flow that stops is visible in run history. A flow that half-finishes leaves two systems disagreeing, so design the handlers, retries and owner first.

Most CMDBs are partly wrong, and the workarounds cost more than the errors. Where the effort pays: identification, relationships, precedence, retirement.

Route every step to a security group rather than a person, delete the approvals nobody has ever rejected, and let conditions skip the rest.

Function access decides what someone can do. The security profile decides whose records they do it to. Most Fusion HCM exposures live in that gap.

Preview status belongs to the instance rather than a setting, so the sandbox you test a seasonal release in has to be planned months before the notes land.

Most slow NetSuite saved searches read far more than anyone needs and throw it away. Fix the date bound and the filter placement first.

A portal is fast on an administrator's laptop and slow on a customer's phone. Fix permission scope, list design and image weight before launch.

A permission role says what may be done and a group says who does it. The assignment binds granters to a target population, and that pairing is where access breaks.

Model queues on kinds of work, pin down the order your assignment rules evaluate in, and give every request that matches nothing a queue someone opens daily.

Build where the work persists, rehearse the promotion, version every build, and decide who can switch the app off before anyone needs to.

Capacity, priority and presence decide how Omni-Channel behaves at peak. Set them from real numbers, then test with two agents and one saturated queue.

An account hierarchy records a commercial relationship. Case visibility is a separate decision, and the hierarchy setting is the one that leaks a child's cases.

Most slow Workday reports retrieve far more than the question needs and then discard it. Fix the data source and the filters before you touch the columns.

The scripts and business rules inside your instance outlive whoever wrote them. Record why the logic exists, keep it in one place, and fail loudly.

Most Dataverse growth comes from attachments, audit rows, trace logs and environments nobody deleted. The per-table view in the admin center names yours.

Writing the two week handover runbook exposes every job only you can run, and the page telling your stand-in what not to attempt is the one that saves you.

Hypercare catches the loud failures. Notification rules that never fire, one-person assignment groups and SLA clocks on the wrong schedule wait for week two.

Three tenure calculations, three headcount numbers, one leadership meeting. A method for auditing Workday calculated field sprawl before reports time out.

A working method for auditing Salesforce profiles and permission sets, and removing the access you find without breaking someone's Monday.

A first-person audit method for finding duplicate Workday security groups, tracing mystery access back to its origin, and setting a review cadence that sticks.

Oracle and SAP both ship bundles where nearly every entry claims top severity. Here is the four-question order I actually use to triage them for real.

A practical method for catching Workday comp cycle configuration drift before go-live, built around an approval step that quietly survives the manager it was written for.

A working rule for deciding which Power Platform solutions get their own dev, test, and production environments, and who approves promotion between them.

The four numbers a platform owner needs before a Power Platform, Dynamics 365, or Agentforce repackaging note gets forwarded to finance.

When a shared Power Automate flow fails, find the work that stopped, name one lead, and write the ServiceNow record before anyone resubmits a run.