AB-100 maintenance pilot - October 4, 2026¶
This single-certification pilot improves the AB-100 guide with an original grounding worksheet, two explained knowledge checks, and developer/deployer responsibility practice. There are now 14 architecture exercises and 24 answered checks. It is a bounded AI maintenance follow-up for learning the concepts and preparing to pass the certification. It is not a new complete technical audit, independent review, or tenant validation. Tenant testing and independent review are best-effort improvements; the fact that they were not performed does not by itself block source-supported study use. No recurring run was created; nothing was merged.
The local checkout was identified by its exact GitHub remote, was clean, and matched remote main at 149bd8ce7a7349b3d7069abd8a110be66e46b69e. Work uses maintenance/ab100-pilot-2026-10-04. No repository AGENTS.md or .agents/skills was found; .github/copilot-instructions.md, contribution, automation, content, source-quality, intake and guide-quality rules were read. September 27 deep-review/learning evidence and September 28 prerequisite/lab follow-ups were inspected. Historical evidence remains intact.
Current and future objectives¶
The saved July 22, 2026 objective baseline remains accepted. Microsoft still announces October 14, 2026 for the English revision and displays that future outline. The September 27 review already mapped all 74 detailed objectives and identified editorial changes. This pilot compares the newly fetched candidate without replacing accepted snapshots or advancing the full-review date. A successful fetch does not establish that a future version is already effective.
The exam page still includes MB-280 and PL-200, while the credential page omits both. The unrelated information-protection summary also remains. The dated guide caveat is retained; no ambiguous credential eligibility was declared valid. The existing October 5 repository review event remains unchanged and is not a newly scheduled automation.
Improvements and objective mapping¶
| Improvement | Published July objective fit | Direct versus adjacent learning | Guide locations |
|---|---|---|---|
| Applicability versus permission, missing metadata, encrypted-file and transcript evidence boundaries | Plan: review data for grounding; design: data processing for grounding and Teams/SharePoint solution design; deploy: test agents and access controls on grounding data | Direct: relevance, test design and data access. Related item: the GHCP metadata implementation. | Part 2, Exercise 14, check 23 and readiness checklist |
| Original six-record worksheet with exclusion reasons, including a future-effective document | Same grounding and test/access objectives; the scenario's date policy is locally chosen, not an exam rule | Direct objective practice with original synthetic inputs; no vendor filtering rule or executed service result implied. | Exercise 14 and its answer checkpoint |
| Developer/deployer handover and exception-queue ownership | Deploy: responsible AI principles, governance and security | Direct: governance and responsible-AI reasoning. Related item: this report's developer/deployer framing and handover worksheet. | Part 10 related item, check 24 and readiness checklist |
| Three evaluated resource options with time, ownership, dates, access and limitations | Grounding/design/SharePoint; deploy/monitoring, testing, security and governance | Direct concept practice; optional SDK, GHCP internals and report-specific framing are adjacent learning. | Places to learn and synchronized AB-100 learning-resource entry |
The SharePoint product article confirms the standard-harness source, caller-access, filter and evidence limitations. The CAT article is accepted as Microsoft CAT blog-documented behavior - VERIFY CURRENT, with an October 4 review date, for the GHCP implementation example. The two articles describe different harnesses, so their different filter surfaces are not treated as a contradiction. No tenant testing by this library or separate matching product-reference contract is claimed. Existing governance and evaluation documentation remain primary product references. Actual conflicts, such as the prerequisite lists, retain both sources and dated notes for later reconsideration.
Bounded candidate decisions¶
Five supplementary resources were evaluated, covering blogs, GitHub/lab material, a report and a video companion. Three additional primary-documentation leads were inspected: SharePoint knowledge (accepted), an attempted GHCP knowledge URL (unavailable through the browser, not used), and Prompt Shields (not adopted because it did not close this pilot's selected gaps). Eight distinct resource candidates total, below the ten-candidate cap. README, lesson and license files are supporting evidence within one repository evaluation, not separately endorsed resources. Broad search returned irrelevant results, so discovery continued through exact Microsoft-owned pages and repositories; irrelevant snippets were not treated as reviewed candidates.
| Resource | Decision and objective fit | Evidence and limitation |
|---|---|---|
| Adi Leibowitz: SharePoint metadata filtering | Accepted supplementary reading; plan/grounding, design/SharePoint, deploy/testing | September 1 publication / September 2 update, 2026; 7-minute publisher estimate; CC BY 4.0. Internal tools are explicitly unstable. No tenant validation or copied code/images. |
| Microsoft AI Agents for Beginners | Accepted selected lesson/lab starting point; deploy/security, monitoring and testing | README, lessons 6 and 10 and MIT license inspected. No separate lesson dates displayed. No notebook or video execution. Lesson 6 inline poem approval follows generation; it is not an enforced pre-action tool boundary. |
| Microsoft 2026 Responsible AI Transparency Report web summary | Accepted supplementary report context; deploy/responsible AI and governance | Vendor self-report, not an independent audit or service-control contract. Full PDF unreviewed. No separate publication/update date displayed. Canonical redirect used. |
| Giorgio Ughini: migration video companion | Rejected for promotion in this pass; potential design/harness and deploy/ALM fit | July 14 / August 2, 2026; companion readable, recording not watched. Experimental unsupported plugin; no setup or migration executed. Recorded rejected intake prevents silent re-recommendation. |
| Microsoft Copilot Studio Samples | Rejected broad-catalog endorsement; potential design/extensibility and deploy/testing fit | README only. Legacy lab relocation and pending-deprecation sample are visible. No narrow sample, dependency path or license fully evaluated. Reconsider an exact current lab with evidence. |
Accepted URLs were checked against the master catalog and were not duplicates. Four new entries (three supplementary resources and one primary product reference) have live source-health observations. None of the reviewed resources showed dump, recalled-question or guaranteed-pass signals; no protected content was copied. Rejections are evidence/selection decisions, not allegations of exam-integrity violations.
Validation and remaining work¶
Exact fetch timestamps, response hashes, before/after guide hashes, preserved prior source-validation metadata, candidate decisions, commands and results are in the pilot ledger. Local raw source bodies stay in ignored .maintenance/ab100-pilot-2026-10-04/.
Current tracked guide-link evidence is 82 distinct URLs: 77 reachable, five access-blocked, zero missing/error. Four new URLs were checked live; the other statuses are historical tracked observations, not a new full-link content review. Blocked/gated commercial content and prior runtime metadata remain unresolved and are not renewed purchase recommendations.
The final validation gate and fresh offline lab results are recorded in the ledger. The Python fixture exercises synthetic gate logic and arithmetic only. The new grounding worksheet is a tabletop; no SharePoint, Copilot Studio, Foundry, notebook, paid course, account-specific eligibility or external video execution was performed. Human/independent practitioner review and tenant testing were not performed. They would strengthen the evidence when feasible but are not automatic blockers to learning from this guide. The prerequisite discrepancy remains a real unresolved credential-eligibility question. GHCP metadata behavior is attributed to the accepted CAT account; a matching product reference or disposable-tenant observation would further corroborate it.
No new full deep-review receipt is issued. Historical full-review dates and hashes remain unchanged; the queue can recognize that the guide changed since its full review. Model identity, token count and credit consumption are unavailable in this execution environment; no estimates are substituted. Branch/commit/PR and exact remote-CI verification are reported with the completed delivery.
Learning-evidence clarification - October 4, 2026¶
The current guide and summary now distinguish direct objective practice from adjacent implementation learning, and blog-documented behavior from independently tested behavior. Microsoft sources remain primary, with evidence weighed at the specific claim and harness level. The CAT article remains accepted. Candidate decisions and the eight-candidate discovery scope are unchanged. Earlier deep-review reports and the original pilot execution ledger retain their historical wording; this clarification does not assert that a tenant test, human review or fresh source fetch occurred. Relevant final publication checks are recorded in the clarification ledger and draft PR.