> ## Content Index > Fetch the complete content index at: https://todayfixtech.com/llms.txt > Use this file to discover other available public pages before exploring further. # Microsoft Planner advanced settings: configure for your team - URL: https://todayfixtech.com/microsoft-planner-advanced-settings/ - Published: 2026-10-31T06:24:32.000Z - Updated: 2026-10-31T06:24:32.000Z - Author: Md Sojib Mia - Tags: Microsoft If you [need to change Microsoft](https://todayfixtech.com/customizing-microsoft-365-dashboard/) Planner advanced settings now: tenant-wide controls live in the Microsoft 365 admin centers and plan-level controls live in Planner or the Microsoft 365 Group UI. Change tenant defaults from Microsoft 365 admin center > Settings > Services & add-ins > Microsoft Planner, and control sharing and guest access through SharePoint sharing policies and Azure AD guest settings. Plan-level membership, task creation and buckets are managed inside the Planner plan, the associated Microsoft 365 Group, or Teams. ## Where are the advanced settings located - Global locations you must check before changing Planner behavior. - Microsoft 365 admin center: tenant-level Planner settings. - SharePoint admin center (via the Microsoft 365 admin center): site-level sharing that affects plans stored in group SharePoint sites. - Azure AD / Groups settings: controls group creation and guest behavior which affect Planner plans tied to groups. - Planner UI (web or Teams): plan-level membership, bucket/task limits, and plan-specific controls. Prerequisites - An account in one of these roles: Global administrator, Microsoft 365 admin, SharePoint administrator, or Groups administrator. - Access to the Microsoft 365 admin center at `admin.microsoft.com` and to the SharePoint admin center via the admin center menu. - A non-admin test user to verify end-user behavior after changes. Where to look (exact paths) 1. Microsoft 365 admin center — Planner (tenant-level) ```text Microsoft 365 admin center > Settings > Services & add-ins > Microsoft Planner ``` Settings path 1. Microsoft 365 admin center — Org settings that impact Planner (group creation) ```text Microsoft 365 admin center > Settings > Org settings > Services ``` Settings path 1. SharePoint admin center — external sharing (affects plans on group sites) ```text Microsoft 365 admin center > Admin centers > SharePoint > Policies > Sharing ``` Settings path 1. Azure AD — Guest and group settings ```text Azure Active Directory admin center > Groups > General settings ``` Settings path 1. Planner UI — plan membership and plan-specific controls ```text Planner (tasks.office.com or Planner in web app) > Select plan > Plan settings or open the group's settings in Outlook or Teams ``` Settings path ## Which advanced options matter and what they do Lead with the controls you can actually change and what effect each has. - Plan creation scope: who can create Microsoft 365 Groups (and thereby Planner plans). Consequence: restricting group creation prevents users from creating new plans. - External sharing / guest access: controlled in SharePoint and Azure AD guest settings. Consequence: limiting or blocking external sharing removes or restricts guest access to plan boards, attached files and group sites. - Plan-level member roles: Owner vs Member. Consequence: Owners can delete plans and change membership; members can create and assign tasks depending on tenant policies. - Retention and data location: controlled in Microsoft Purview/Compliance and SharePoint. Consequence: retention policies determine how long Planner task data is kept and when it is disposed of. - Task and bucket limits: Planner has practical limits (plan size, attachment sizes) enforced by the service; some limits are affected by SharePoint site limits because attachments are stored in the group site. - Creation defaults and templates: Planner does not expose many tenant-level template switches; templates and provisioning are normally handled per plan or with automation. - Exchange and Teams policies: messaging, attachments and connectors are subject to Teams and Exchange policies; those policies affect Planner attachments and notifications. If you need to change one of these, use the step-by-step sections below for the relevant service. ## How to change a tenant-level setting step by step Restricting external sharing can break guests’ access to many existing resources (Teams, SharePoint, Planner). Notify impacted teams before you change it. This example shows how to tighten external sharing so guests lose access to group-connected Planner plans. Required role: Global administrator or SharePoint administrator. 1. Sign in to the Microsoft 365 admin center as a Global admin. 2. Open the SharePoint admin center. ```text Microsoft 365 admin center > Admin centers > SharePoint ``` Settings path 1. In the SharePoint admin center, open Policies > Sharing. ```text SharePoint admin center > Policies > Sharing ``` Settings path 1. Set the default sharing for sites connected to Microsoft 365 Groups to a more restrictive option such as `Only people in your organization` and save. 2. Confirm Azure AD guest settings to prevent new guest invitations if you want to block guest access entirely. ```text Azure Active Directory admin center > Users > External users > User settings ``` Settings path 1. In Azure AD, toggle the guest invitation options or adjust Collaboration restrictions to block specific external domains. 2. Wait for propagation. Expected timing: changes to SharePoint and Azure AD commonly propagate within minutes but can take up to 24 hours for all tokens and caches to expire. 3. Verify Planner behavior with a test user as described in the verification section. Expected result: guests lose access to Planner plans hosted on group SharePoint sites and sharing UI options are limited. If your tenant exposes Planner-specific toggles, use this path to change them: 1. Sign in to admin.microsoft.com. 2. Go to Settings > Services & add-ins > Microsoft Planner. ```text Microsoft 365 admin center > Settings > Services & add-ins > Microsoft Planner ``` Settings path 1. Edit the options shown there (for example, plan creation toggles), save, and allow time for changes to apply. Not all tenants show granular Planner toggles on that page; SharePoint and Azure AD settings are the more reliable controls for sharing and guest behavior. ![A close screenshot-style photo of the Microsoft 365 admin center sharing settings page with the cursor over the external sharing option.](https://tse1.mm.bing.net/th?q=screenshot-style%20photo%20of%20Microsoft%20365%20admin%20center%20sharing%20settings%20page%20with%20cursor%20over%20external%20sharing%20option&w=624&h=352&c=7) ## How to change plan- or group-level settings and exceptions Plan-level changes are done in Planner, Teams, or the [Microsoft 365 Group settings](https://todayfixtech.com/microsoft-365-security-features/). These can sometimes look like they override tenant intent for a specific plan but they cannot bypass tenant blocks. 1. Open the specific plan in Planner web at `tasks.office.com` or open the plan tab in Teams. 2. To change membership and owner status: 3. Open the plan and click the members header or the group name to open the group card. ```text Planner > Select plan > Group name or Members ``` Settings path 1. Add or remove owners and members from the group. Expected result: owners can manage membership and plan settings immediately for the plan. 2. To adjust who can create tasks or buckets, change membership roles; Planner uses the group's owner/member roles for permissions. 3. To change site-level sharing for a single group's SharePoint site (an exception): Making a group site more permissive than tenant policy can expose sensitive data. Confirm approvals before loosening sharing. 1. In the SharePoint admin center go to Sites > Active sites. ```text SharePoint admin center > Sites > Active sites > Select the group-connected site > Sharing ``` Settings path 1. Change the sharing level for that site only (for example, allow `Anyone with the link`) if allowed by tenant policy. Expected result: that group's site accepts broader sharing links; tenant-wide blocks still apply. 2. Example — add buckets or tasks in a single plan (no admin change required): 3. Open the plan and choose `Add bucket` to create more buckets. 4. Attach files to tasks; if attachments fail, check the group's SharePoint site storage and file size limits. Notes on overrides - Tenant-level policies in SharePoint and Azure AD are authoritative for guest access; site-level settings can be more restrictive but not more permissive where the tenant blocks external sharing. - Group owners can add members and invite guests only if tenant policies allow guest invitations; they cannot bypass a tenant block on external sharing. ## Why my changes didn’t take effect and how to fix it Common causes when a change doesn't appear to apply and quick fixes. - Propagation delay: Many admin changes take minutes to hours to propagate; sometimes up to 24 hours. - Cached credentials or client state: Planner web and Teams cache tokens and UI state. Fix: sign out, clear browser cache, or use an incognito window to check the new behavior. - Wrong admin role: You might not have the needed role. Example: a SharePoint admin can change sharing but cannot change Azure AD guest invitation settings. Fix: Check your [role in the Microsoft](https://todayfixtech.com/microsoft-365-updates-features/) 365 admin center or ask a Global admin. - Conflicting policies across services: A SharePoint sharing policy might be permissive while Azure AD blocks guest invitations. Fix: Check both SharePoint sharing and Azure AD External Collaboration settings and align them to your intent. - Licensing limitations: Some compliance and retention controls require specific licenses. If retention behavior is missing, verify assigned licenses. Fix: Confirm assigned licenses in Microsoft 365 admin center > Billing > Licenses. - Teams or Exchange transport policies: If attachments or connectors fail, an Exchange or Teams policy may be blocking content. Fix: Review Teams messaging policies and Exchange transport rules. How to diagnose quickly 1. Reproduce the setting change with a test user who has the same license and role as impacted users. 2. Use an incognito browser session to remove cached tokens. 3. Check admin audit logs in the Microsoft Purview compliance portal for the change and any errors. ```text Microsoft Purview compliance portal > Audit > Search ``` Settings path 1. If a guest still has access after a block, verify the guest’s membership source: guests added before the change might retain access until removed. ## How to verify, test, and revert changes safely A safe verification workflow and rollback plan you can run in 15–30 minutes. Verify and test steps 1. Create or identify a non-admin test user and assign the same licenses as real users. 2. Sign in as the test user in an incognito browser to avoid cached tokens. 3. Reproduce the exact action affected by your change. Examples: 4. Try to create a new plan or Microsoft 365 Group. ```text Create new plan in Planner or create a new Microsoft 365 Group ``` Expected action 1. Try to access a plan as a guest after restricting external sharing. ```text Open plan URL as guest user ``` Expected action 1. Check results in admin logs for entries that confirm the setting applied. ```text Microsoft Purview compliance portal > Audit > Search ``` Settings path 1. Verify SharePoint site-level sharing status for affected group sites. ```text SharePoint admin center > Sites > Active sites > Select site > Sharing ``` Settings path How to revert safely Reverting a global sharing block will re-enable access for guests; prepare a communications plan. 1. Record the original settings before you change anything. Quick method: copy the relevant setting pages to a text file or take screenshots of the values. 2. If the change caused breakage, revert the specific setting you changed first (for example, set SharePoint site sharing back to its previous level). 3. If you changed multiple services (SharePoint and Azure AD), revert them in the same order you applied them, verifying after each revert. 4. After revert, force a cache refresh for a test user by signing out and signing in again, then re-run the verification steps. Completion checks - Test user behavior matches the intended change (for example, guests are blocked or plan creation is prevented). - Admin audit logs show the change and no error entries. - A sample of real users confirm they see the expected UI and permissions. If things still look wrong after revert, escalate to Microsoft support with the tenant ID, change timestamps and audit log entries. ## Conclusion Make changes one service at a time, record the original settings, and verify with a non-admin test account. For sharing and guest controls, the authoritative controls are SharePoint sharing policies and Azure AD guest settings; Planner UI handles plan membership, owners and per-plan actions. If propagation seems slow, clear client caches and check audit logs before making more changes. When you need to roll back, revert the recorded settings and retest with the same test user. ## Frequently Asked Questions ### Which admin role can change Planner tenant settings? Global administrator or Microsoft 365 admin can change tenant-level Planner settings. SharePoint administrator can change SharePoint-level sharing that impacts Planner; Groups administrator controls group creation policies. Some changes require multiple roles to change related settings across services. ### Will restricting SharePoint external sharing immediately block guests from Planner? Not always immediately. Changes commonly propagate within minutes but can take up to 24 hours for all tokens and caches to expire. Ask affected users to sign out and sign back in and test with a guest account in an incognito browser. ### Can a plan owner override tenant-level external sharing blocks? No. Tenant-level blocks in SharePoint or Azure AD are authoritative. A site owner can make a site more restrictive but cannot bypass a tenant-wide block to make it more permissive. ### How do I check what actually controls a specific Planner plan? Check the associated Microsoft 365 Group membership (owners vs members), the group's SharePoint site sharing level in the SharePoint admin center, and Azure AD guest settings. Then reproduce actions with a test user to confirm behavior.