Friday, 3 April 2026

TeamViewer’s new Intune connector guidance covers Android, iOS, and Windows

The period’s clearest substantive item is new Intune guidance for a TeamViewer remote-assistance experience. It covers all listed Android enrollment options, iOS/iPadOS, and Windows, and documents connector setup, licensing, permissions, and data sharing. The evidence does not classify the capability as preview or generally available. Other meaningful updates clarify compliance-report interpretation, correct a Windows Autopilot proxy example, and expand Configuration Manager upgrade guidance. Security-baseline changes shown here only update publication dates, while other edits fix links or wording.

• Intune · Fundamentals

  New TeamViewer connector experience is documented for Intune

  A new how-to describes configuring the new TeamViewer connector, starting remote-assistance sessions, and the data Intune shares with TeamViewer. The documented scope includes Android BYOD, COSU, COBO, COPE, AOSP, and DA enrollment options, plus iOS/iPadOS and Windows. The article requires an eligible TeamViewer license and notes that GCC and GCC High are unsupported; the evidence does not establish preview or general-availability status.

• Intune · Fundamentals

  Compliance reporting guidance will clarify check-in and user-state edge cases

  The In Development page says Intune will add guidance explaining that compliance reports refresh during device check-in and policy-refresh cycles; shared-device reports show the last user who checked in; Pending can persist until the next reporting cycle; multiple user and system records can appear; and summary and detailed views may temporarily differ. This is documentation clarification, not evidence of a new reporting behavior.

• Windows Autopilot · Device enrollment

  Autopilot proxy XML now shows an HTTPS scheme

  The Hybrid Connector Proxy example changes the proxyaddress value from `<PROXY ADDRESS HERE>:<PORT HERE>` to `<https://PROXY ADDRESS HERE>:<PORT HERE>`, leaving the other shown attributes unchanged. The diff corrects the documented example but does not establish a runtime behavior change or a requirement to modify existing configurations.

• Configuration Manager · Windows

  Configuration Manager guidance adds Windows Server 2025 upgrade paths

  The supported upgrade guidance now lists Windows Server 2019 to 2022 or 2025; Windows Server 2016 to 2019, 2022, or 2025; and Windows Server 2012 R2 to 2016, 2019, or 2025. It also adds an important requirement that site systems running the Software Update Point role use the same Windows Server version for synchronization, including relevant Central Administration and primary site servers with WSUS Administration Tools.

This period briefing was generated by AI from the tracked Microsoft Learn and Message Center changes.