Connect Version History Archive
Doc updateThe 1.3.20.0 release notes no longer list support for Enterprise Administrator credentials from a child domain.
Daily.Entra.NewsNovember 20 was mostly a documentation-maintenance day: 74 items were updated, none were added or removed, and one Message Center announcement appeared. The substantive changes cluster around Agent ID: Microsoft now spells out CIMD and MCP endpoint, scope, discovery, authorization-server, audience, compatibility, and consent guidance, while Copilot Studio’s Dataverse agent-user capability is scheduled for general availability on December 8, 2026. ID Governance also documents a second dynamic-permissions preview. Most remaining edits are formatting, link, example, or reference maintenance, with a few targeted corrections such as the Global Secure Access hostname.
A Message Center announcement says Copilot Studio will be able to create Dataverse agent users with the Microsoft Entra agent’s user account, reaching general availability on December 8, 2026.
The configuration guidance now requires a nonempty MCP endpoint path without a trailing slash, fully qualified delegated scopes, `organizations` for multitenant authorization servers, and the resource application’s client-ID GUID as the token audience. During preview, it says not to use client secrets or private-key assertions.
The Secure MCP Server with Entra ID guide now specifies canonical MCP endpoint URLs, metadata discovery through the server origin and the `WWW-Authenticate` header, fully qualified scopes, and v2 token values: the resource application’s client-ID GUID in `aud` and the short scope name in `scp`.
The CIMD client guidance now describes default, strict, and open tenant-consent postures, including their approval and OAuth-scope behavior. It warns that unrestricted consent can enable consent phishing and unauthorized data access, and recommends the strict posture where client onboarding requires administrative review.
The updated overview explains a preview in which agents request permissions for specific tasks based on intent. Requested privilege levels, separation-of-duties conflicts, and organizational policy inform those requests.
This period briefing was generated by AI from the tracked Microsoft Learn and Message Center changes.
The 1.3.20.0 release notes no longer list support for Enterprise Administrator credentials from a child domain.
The page was updated while retaining guidance on ADSyncConfig, required AD DS permissions, RSAT, PowerShell commands, and targeted AD object configuration.
The page reorganizes attribute and role lists and improves formatting for ADSyncTools command output and PowerShell examples. It continues to specify ADSyncTools v2.5.0 as the minimum required version.
The reference was refreshed across its function list and function sections, including descriptions, syntax, remarks, and examples.
The custom installation page updates Markdown formatting, including a completed delimiter for the pass-through authentication table row. The surrounding setup guidance remains available.
The roadmap page updates table and list formatting, including links for Pass-through Authentication, hardware and prerequisites, and Health agents.
The tutorial’s setup instructions and PowerShell examples were reformatted while retaining the same commands, IP values, and guidance.
The page removes extra spaces from Ubuntu and RHEL package links. Package versions, URLs, signing-key text, and release information remain unchanged.
The Microsoft Entra Connect staging server guide received formatting cleanup, including corrected list structure and link spacing.
The article received a minor Markdown table-formatting correction. Guidance for directory extensions, application and service principal creation, and custom attribute mapping is unchanged.
The article received minor Markdown formatting and whitespace corrections, including the attribute table header and instructional text.
The page received minor Markdown and formatting updates, including a corrected table row, while retaining its existing Cloud Sync, Connect Health, and V2 prerequisite guidance.
The page now correctly closes the TLS version error table row. The servicing guidance and event-log troubleshooting instructions remain unchanged.
The app consent policies documentation now uses a corrected Markdown link to the Permission grant condition sets reference.
Corrected table-row formatting and link markup in the Microsoft Entra Connect SQL delegation documentation.
The connector Service Manager UI page updates the presentation of scope and Sub-Tree search instructions and their screenshots.
The port tables were updated, including formatting for the HTTPS 443 SSO registration entry and descriptions of required communications.
The page was updated around the private network connector link, endpoint list, and installer command; the displayed values remain unchanged.
Added missing table delimiters to the header and two rows in the version history documentation. The upgrade steps and permissions guidance remain unchanged.
The table entry for federating multiple Microsoft Entra ID instances with one AD FS farm was updated; its displayed link and description remain unchanged.
The Entra Connect Sync overview documentation received a minor formatting update.
The link to Group writeback with Microsoft Entra Cloud Sync was updated to remove an extra space before the closing bracket.
The certificate-based authentication article received minor Markdown formatting cleanup, including a corrected table delimiter. Existing roles, PowerShell examples, mapping guidance, and synchronization notes are presented in the updated page.
The architecture documentation’s two diagram links were reformatted by removing extra spacing before the image markup. The surrounding guidance is unchanged.
The article updates guidance on credential-validation dependencies, passwordless authentication, avoiding single points of failure, and contingencies for large-scale disruptions.
The page’s two diagram links were updated to remove an extra space in their Markdown image syntax.
The documentation includes minor text corrections, including the attribute name changed from “supplementalCrendetials” to “supplementalCredentials.”
The Cloud Sync installation page now has corrected Markdown spacing in the SSPR password-writeback tutorial link.
Two registration URL table rows now include closing cell delimiters, and the 4 MB scoping-limit note has corrected punctuation.
The article was revised in sections covering registered device PRTs, WS-Trust requirements, WAM and browser SSO, PRT validity and renewal, and device-signing-key issuance.
The page’s schema text and Replace example were normalized, and trailing delimiters were added to the `cn` and `objectGUID` table rows.
The alt text for the Support Assistant screenshot now says “create support request” instead of “create support requestion.”
The alert catalog documentation was revised, including guidance for synchronization failures, password hash synchronization, high memory consumption, authentication tests, AD FS connectivity, certificates, service status, and federation DNS.
The page was refreshed while retaining guidance on synchronization behavior, the workflow, and JSON and HTML diagnostic reports.
The Connected System table row now includes an explicit empty column delimiter after “Select the Microsoft Entra Connector.”
The Linux device registration troubleshooting page received a minor formatting change.
The guide received minor text and formatting edits, including cleanup to a related provisioning link. The documented configuration procedures remain unchanged in the supplied diff.
The Entra Connect sync filtering guide updates the formatting and placement of numbered example steps and screenshots for DoNotSync, Sales, and catch-all rules.
The documentation was revised to clarify synchronized attributes, minimum-attribute guidance, the recommended default set, and user attributes added for selected apps.
The documentation updates guidance on secure identifier URI patterns, checking policy status, requesting exemptions, and configuring app management policies.
The reference page updates formatting in the product-name guidance and several licensing table entries, including Dynamics CRM Online Basic, Office 365 Small Business, and Power BI Premium Per User Add-On for GCC.
Adjusted the Markdown formatting for screenshots and diagrams so the linked images render consistently.
The reference adds closing table delimiters to the ProvisioningManagement Execution and EntitlementManagement rows. The surrounding content is unchanged.
The page now explains CIMD’s role in AI agents connecting to MCP servers and adds compatibility tables for tested clients and Microsoft MCP servers, including supported and unsupported entries.
The article now specifies a nonempty MCP endpoint path without a trailing slash, fully qualified delegated scopes, `organizations` for multitenant authorization servers, and that the token audience is the resource application's client-ID GUID. It also says not to use client secrets or private-key assertions during preview.
The guide now specifies canonical MCP endpoint URLs, metadata discovery through the server origin and WWW-Authenticate header, fully qualified scopes, and v2 token claim values.
The access package section heading now correctly spells “identities.”
The `tid` and `idtyp` claim names were corrected to remove extra spaces in the agent token claims table.
The documentation now describes default, strict, and open tenant consent postures for CIMD clients, including their approval and OAuth-scope behavior. It also warns that unrestricted consent can enable consent phishing and unauthorized data access.
We are announcing the ability to create Dataverse agent users with Microsoft Entra agent's user account in Copilot Studio. This feature will reach general availability on December 8th, 2026.
Formatting was cleaned up across the risk detection tables, headings, and links, including the Suspicious MFA authentication approval link.
The Risky Agent documentation adds a missing table delimiter in the risk-detection table.
The guide’s coverage of limitations, SAP BAPI functions, endpoint and schema setup, and SOAP binding requirements was updated.
The entitlement management page received minor text and image-markup updates covering connected organizations, authentication, B2B access, organization updates, and policy scope.
The access review page was revised across reviewer roles, group and application selection, guest access reviews, external identities, and guest self-review instructions.
The page’s existing guidance, links, role list, navigation steps, and screenshots were retained while Markdown formatting was normalized.
The deployment article was updated across existing workflow, provisioning, task, and rollout guidance, with only minor formatting or punctuation changes visible in the supplied diff.
The Workday attribute table now consistently formats all example rows with the required delimiters.
Step numbering and table spacing were standardized on the downloadable review history page.
The stale guest account cleanup guide now consistently formats several access review table rows and examples.
The table row now includes the correct closing delimiter while retaining the same description of agent identity handling.
The documentation now more clearly describes a second dynamic permissions preview in which agents request permissions for specific tasks based on intent. It also explains that privilege level, separation-of-duties conflicts, and organizational policy inform these requests.
The page updates the Markdown formatting for the guest-users-only screenshot link; surrounding documented content is unchanged.
The document’s guidance, prerequisites, links, and scenario descriptions were refreshed; the supplied diff shows the same wording before and after the update.
The deployment guidance continues to cover fraud prevention, account takeover, 30-day log retention, synthetic monitoring, and pricing and billing references.
The article updates Markdown formatting for linked diagrams and related content presentation.
The page’s linked CIAM diagram image markup was cleaned up; the surrounding guidance on user flows, branding, and custom domains remains unchanged.
The deployment scenario page updated the markup for several screenshot links by removing extra whitespace and preserving their lightbox references.
The rules and display definitions page was updated; the visible customer-intent wording about finding information to disable remains unchanged.
The credential design documentation now correctly names the schema.org `EducationalCredential` object in its credential-type example.
The credential-type example now correctly names the schema.org `EducationalCredential` object instead of `EducationaCredential`.
The Workload ID FAQs page received minor whitespace and formatting updates, including adjustments to the features table.
The service principal guidance now uses a valid link to the New-MgServicePrincipal cmdlet documentation.
The considerations article updates its ARM template example and dependency declarations. The documented regional rollout and 409 conflict limitation remain unchanged.
The documentation corrects the hostname pattern from `*.interent.efp.globalsecureaccess.microsoft.com` to `*.internet.efp.globalsecureaccess.microsoft.com`.