Standard users can no longer reorder default Apps collection in My Apps, Global Administrator can

The currently documented behavior is that users can reorder apps only in custom user-created collections; the built-in Apps collection is defined as an alphabetical default collection, so the standard-user error should be escalated only if Microsoft confirms that default-collection reordering remains supported.

Intended behavior in the current documentation

Microsoft distinguishes editing the default collection from reordering its applications:

• The built-in Apps collection contains every application assigned to the user and is sorted alphabetically.
• Users can edit that collection—for example, remove/hide apps and add previously hidden apps—but cannot rename it.
• The reordering instructions are explicitly titled “Reorder apps in your custom user-created collection” and say users can edit only collections they create. ^1^

The Entra product overview is consistent with that distinction. It documents these user customizations:

• Creating personal collections.
• Hiding and reordering collections.
• Removing applications from the default Apps collection.

It does not document manually ordering applications inside the default collection. ^2^

Therefore, the two statements in the support article concern different operations:

• “You can edit the Apps collection” means changing its membership or visibility.
• “You can edit only the collections that you create”, within the app-reordering section, limits manual app ordering to custom collections.

Administrator behavior

The documented administrator model does not establish Global Administrator as a required role for personal reordering of the default Apps collection. For administrator-created collections, the supported roles are Cloud Application Administrator, Application Administrator, or owner of the relevant service principal. Those collections are ordered and managed in:

Microsoft Entra admin center → Entra ID → Enterprise apps → App launchers

Admin-managed collections are managed there rather than in My Apps. ^3^

Consequently, the successful Global Administrator test does not establish a supported permission model for default-collection reordering. It could reflect privileged behavior or a service inconsistency, but the available public documentation does not identify it as an intentional Global Administrator capability.

Do not assign Global Administrator—or another privileged application role—to users as a workaround. The Application Administrator role, for example, can manage enterprise applications and application credentials and can impersonate application identities, making it far broader than this personalization task. ^4^

Tenant control, change notice, and regression status

The published Entra default-user settings do not document a tenant control for allowing standard users to reorder applications inside the built-in Apps collection. The documented restrictions concern operations such as registering applications, creating groups, and reading directory information—not My Apps tile ordering. ^5^

The cited public documentation also does not identify:

• A recent authorization change for this operation.
• A known regression matching this error.
• A Message Center announcement, roadmap item, or service-change notice.
• A supported Entra role that grants standard users this one capability.

Only Microsoft Support can confirm whether the earlier behavior was intentionally changed, an undocumented behavior that was corrected, or a regression.

Collect evidence and escalate

Since the behavior has already been reproduced across multiple standard users and contrasted with a Global Administrator, capture a clean comparison:

1. Record UTC timestamps for one failed standard-user attempt and one successful administrator attempt.
2. Capture the exact collection name, error, browser version, and whether each account is a member or guest.
3. In the Entra admin center, open Entra ID → Enterprise apps → Audit logs.
4. Filter Service to My Apps and export entries around both timestamps. My Apps collection operations are included in these logs, although the documentation does not guarantee that a rejected reorder attempt will create an event. ^3^
5. Open Microsoft Entra admin center → Learn & support → New support request, or use Diagnose and solve problems → Self-Service Support → Create a support request. ^6^
6. Ask Support to confirm:
   • Whether default Apps ordering is still supported for member users.
   • Why Global Administrator succeeds when a standard user receives authorization denial.
   • Whether a backend rollout or incident changed this behavior.
   • Whether the documentation’s “Edit collections” wording needs correction.

Include the tenant identifier and affected-user details only within the private support case, not in a public Q&A post. Microsoft Support and engineering can use tenant configuration, audit/sign-in data, and service telemetry while investigating the incident. ^7^

The supported user workaround is to create a personal custom collection and reorder applications there; that is the only app-level drag-and-drop ordering scenario explicitly documented today.

References

1. Customize app collections in the My Apps portal | Microsoft Support
2. My Apps portal overview
3. Create collections on the My Apps portal - Microsoft Entra ID
4. Microsoft Entra built-in roles
5. What are the default user permissions in Microsoft Entra ID?
6. Find help and get support for Microsoft Entra
7. Microsoft Entra diagnostic logs