IT & AI brief, 26 October 2026: Copilot connector controls and Intune device page

The date to watch this week is 30 October, when Microsoft starts enforcing the Allowed agent types setting on the Copilot Connectors page for every tenant. It was a quiet weekend for new security advisories: the latest CISA alerts we found are from 23 October and are already covered in the previous brief.

Copilot connectors: Allowed agent types is enforced from 30 October

What changed: MC1454973, updated on 23 October, retires the setFederatedConnectors CLI toggle that controlled Microsoft 365 Copilot connectors. The toggle was deprecated by 25 August 2026. From 30 October 2026 the Copilot Connectors page enforces the Allowed agent types tenant setting for all tenants.

Who is affected: Admins who govern Copilot connectors, especially anyone with scripts or runbooks that call the old toggle. Tenants that never used it can ignore the message.

What to do: Open the Microsoft 365 admin center, go to Agent 365, then Allowed agent types, and check that the configuration matches the posture you want before Friday. Tenants that take no action fall under the existing default. Tell the teams who manage Copilot and security governance. See also /blog/copilot-connectors-external-data-setup.

Intune: the new device page is now the default

What changed: MC1456780, updated on 23 October to clarify permissions, says the single device page in Intune replaces the legacy page, which is no longer available. The change took effect with the 2609 service release.

Who is affected: Every admin who opens a device from Devices, then All devices. Admins without the Managed devices/Update permission may be unable to do some actions, such as renaming a device. Changing or removing a primary user also needs Managed devices/Set primary user.

What to do: Review custom Intune roles and add the permissions each task needs, then update help desk documentation and screenshots. If a technician reports a missing button, check their role first.

Teams meeting notes will be stored in the organizer's OneDrive

What changed: MC1523076 (23 October) says new Loop and Facilitator notes in non-channel Teams meetings will be saved in the organizer's OneDrive for Business, in the Meetings folder, rather than in the OneDrive of whoever started the notes. Rollout begins mid-November and should finish in late November 2026. Existing notes stay where they are, and channel meetings are unchanged.

Who is affected: Meeting organizers, who will own the files, and every tenant that has retention, data location or offboarding processes tied to the note-starter.

What to do: No configuration is required. Review retention and leaver procedures so they cover organizer-owned notes; /blog/onedrive-access-after-user-leaves and /blog/purview-retention-policies-guide help here.

Teams admin center adds AI meeting-quality insights

What changed: MC1523077 (23 October) adds insights to Teams admin center, under Meetings, that flag unusual meeting-quality patterns by location or public IP. It points to likely causes in the network, the client device or the headset or camera, with suggested fixes. Data refreshes daily. Rollout starts mid-November and finishes by early December 2026 (mid-December for GCC). SIP phone, PSTN and peer-to-peer call data are excluded.

Who is affected: Global, Teams, and Teams Communications administrators and support roles. The post lists no licence requirement.

What to do: Nothing to enable. Once it appears, use it to triage call-quality tickets, and note that it analyses existing data, so check that your AI governance notes cover it.

GitHub Apps can now be installed on an enterprise

What changed: GitHub made enterprise installations of GitHub Apps generally available on 23 October. New permissions cover enterprise policies and rulesets, two-factor requirements, domain verification, IP allowlists, enterprise profile and member privileges. These let automation that used classic personal access tokens run as an app instead. The page says some of this arrives on GHES in version 3.24.

Who is affected: Enterprise and organization owners with scripts that rely on classic PATs, and platform teams on GitHub Enterprise Cloud.

What to do: List the PATs used for enterprise automation, create an app with only the permissions each job needs, and install it on the enterprise. Details: GitHub changelog.

Also worth knowing

• Gemini Notebook is now a Connected App inside the Gemini app, so users can create and query notebooks from chat: Workspace Updates.
• GitHub's usage metrics API now reports activity from third-party coding tools such as OpenCode: GitHub changelog.
• Copilot in Microsoft Teams can turn notifications into code: GitHub changelog.