Bug fixes in Microsoft Access - Current Channel Version 2605 (Build 16.0.20026.20118)
Bug Name Issue Fixed Edge Browser Control didn't render PDFs on some machines When the Edge Browser Control was used to display a PDF, on some machines the PDF would not render at all if the registry value "HKEY_CLASSES_ROOT\.pdf\Content Type" was missing. Access now provides the missing content type, so the Edge Browser Control can render the PDF. Export to SharePoint failed for tables with both lookup fields and attachment columns When exporting an Access table to a SharePoint list, if the table contained both a lookup field and an attachment column, the export could fail with an error. The export now handles this combination correctly, so the export completes successfully. Conditional Formatting color picker showed a reduced palette in Version 2604 A regression introduced in Version 2604 caused the Conditional Formatting color picker to display a smaller set of color choices than previous versions. The full legacy color palette has been restored. Some Unicode characters displayed incorrectly in objects exported to Excel When exporting an Access object whose name contained certain extended Unicode characters, the resulting file's sheet name displayed the characters incorrectly. These characters are now preserved correctly during export. Power BI Gateway couldn't refresh semantic models from .accdb files Refreshing a Power BI semantic model that connected to a .accdb file via the on-premises gateway could fail with "Unspecified error". Connection setup has been adjusted so the gateway can successfully refresh the model. Monaco SQL view: Ctrl+Z didn't undo Ctrl+Shift+K line deletion In the new Monaco-based SQL editor, pressing Ctrl+Shift+K to delete the current line removed the line, but a subsequent Ctrl+Z would not restore it. Undo now works correctly for this and similar editing operations. Document tab text didn't scale with Windows text-size setting When the Windows display setting for text size was increased, document tab labels and the record navigation bar continued to render at the standard size, while other Access UI scaled correctly. The document tabs and record navigation bar now honor the system text-size setting. Error when editing a Long Text field after a write conflict When a write conflict occurred on a record containing a Long Text field, subsequent attempts to edit the field could fail with an error. The data path now refreshes the cached field values correctly after a conflict so that further edits succeed. Access terminated unexpectedly when reading Edge Browser Control properties in form design view In form design view, retrieving the ReadyState or LocationUrl property on an Edge Browser Control could cause Access to terminate unexpectedly. Both properties now return safely in design view. "Copy" prefix was prepended instead of appended to copied object names When duplicating a database object, Access named the copy "Copy of Form1" instead of "Form1 - Copy". This made copies of related objects sort apart from their originals in the Navigation Pane. Copy-of names now append the suffix, so related objects stay together when sorted alphabetically.Zoom in or out of forms, tables, and queries when in Form View or Datasheet View
Access now lets you zoom in and out when you’re working with forms, tables, and queries in Form View or Datasheet View. Zoom in for a closer look at your data or zoom out to see more on screen at once. You can adjust the zoom level using the Zoom button on the ribbon, the zoom slider on the status bar, or keyboard shortcuts. Zoom is also available in Print Preview for reports. Zoom isn’t supported in Report View or Design View. This feature is available in Access for Microsoft 365, version 2605 and later. Choose a magnification setting from the ribbon On the Home tab, select Zoom and choose one of the following options: 50%, 75%, 125%, 150%, 175%, 200%, or 500%. To return the view to 100% zoom, click Zoom 100%. If you prefer to use the keyboard, you can press Ctrl + Alt + 0 (zero). Use the zoom slider to quickly zoom in or out On the status bar in the lower right-hand corner of Access, select the zoom slider. Slide to the percentage zoom setting that you want. Press – or + to zoom in gradual increments. Use zoom keyboard shortcuts or mousewheel To zoom in, press Ctrl + Alt + Plus (+). To zoom out, press Ctrl + Alt + Minus (-). To return to 100% magnification, press Ctrl + Alt + 0 (zero). To use the mousewheel and scroll to zoom in or out, press Ctrl + mousewheel. Change your default zoom percentage Access doesn't save zoom settings on closing and reopening a form. Instead, it opens your form using the default zoom setting. To set your zoom default percentage, choose File > Options > Current Database > Application Options and choose the Default Zoom setting. Note Content inside of ActiveX controls, such as the text in a TreeView control, doesn't resize when zoomed. Zooming in Access only affects Access-native controls. If a form uses ActiveX controls, consider replacing them with native Access controls so they scale with the rest of the form.Make any agent enterprise-ready with the Agent 365 SDK
One of the biggest barriers to enterprise adoption is the lack of centralized controls. Before deploying an agent broadly, organizations need clear answers: What is this agent allowed to do? What data can it access? How is it monitored? And how do we step in when something goes wrong? Today, developers often piece together identity, runtime protection, and observability using a mix of point solutions and open-source tools. The result is fragmented policy management, disconnected monitoring, and operational overhead that’s difficult to scale within existing IT and security systems. What enterprises need instead is a unified control plane that brings these capabilities together. Introducing the Agent 365 SDK On May 1, Microsoft announced the general availability of Agent 365, the control plane for enterprises to observe, govern, and secure agents at scale. Agents built on the Microsoft AI platform (Agent Builder, Copilot Studio, and Microsoft Foundry) get Agent 365 capabilities automatically, with zero additional developer effort. For agents built on external platforms or open-source frameworks, the Agent 365 SDK provides the path in. The SDK enables enterprise-grade observability, governance, and security, while the Agent 365 CLI provisions the agent identity and registers the agent in Agent 365 from day one. For example, a back-office agent built on Microsoft Foundry and a customer-facing agent built with the OpenAI Agents SDK can both be managed through Agent 365, using the same identity model, observability signals, and policy engine, no matter which platform or framework on which the agent runs. What you get with the Agent 365 SDK Observability A unified agent registry. Every agent registered through the SDK appears in a unified Agent 365 registry, giving admins visibility into ownership, usage, connected tools and knowledge sources, and assigned permissions. Additional signals also help surface unmanaged local agents in the same control plane. Security Operations Center (SOC) visibility in Microsoft Defender. Security Operations Center teams can use Microsoft Defender telemetry to hunt across agent activity, identify vulnerabilities, and investigate potential risks across the entire agent fleet Governance Agent lifecycle management. Apply rules-based policies to automatically expire inactive agents, flag ownerless agents, and block risky ones. Onboarding and agent governance. Deploy agents to specific users or groups only after permissions, policies, and reviews are complete. Block, unblock, or remove agents on demand to control availability. Policy templates. Group existing policies from Entra, Purview, Defender, and SharePoint into reusable templates that apply automatically during agent approval or onboarding. Tool controls for agents. View, allow, or block tools across the tenant so agents only use approved tools, enforcing consistent governance without per-agent configuration. Security Agent identity in Entra. The SDK generates an agent identity in Entra so the agent can be managed, and policies and role assignments can be applied to it the same way they are applied to users. Learn more in our Entra Agent ID developer blog post. Access control. Agents can be secured by Entra Conditional Access and Identity Protection for runtime protections as agent behavior evolves. Threat detection in Defender. Agent activity surfaces in Microsoft Defender alongside the rest of the estate, with alerts wired into the same incident pipeline the SOC already runs on. Threat blocking tool invocation. When you register tools with Agent 365, calls to and responses from those tools are protected by Defender’s runtime protection, blocking high-risk tool calls and actions before they execute. How companies are putting it to work Many software companies have already integrated the Agent 365 SDK into the agents they build, spanning three primary categories. The first is AI-native software vendors building customer-facing agents, such as Genspark, Zensai, Egnyte, and Zendesk. The second includes agent platforms and “agent factories” where customers build and run their own agents, including Kore.ai, Kasisto, and n8n. And the third is enterprises developing custom internal agents for their own employees and business processes. All three groups integrate with the Agent 365 SDK for the same reason: when these agents are deployed into an enterprise, organizations can immediately observe, govern, and secure them in Agent 365 with no additional work required for the core capabilities. More advanced scenarios such as data security and compliance can then be added through Microsoft Purview APIs when required. Two examples of what this looks like in practice Kore.ai is an enterprise platform for building and managing AI agents and assistants. Raj Koneru the CEO of Kore.ai had this to say about Agent 365: "Enterprises can easily build AI agents today but scaling them with trust and governance is where most initiatives stall. With Kore.ai deeply integrated into Microsoft Agent 365, identity, security, and governance are built in from the start, empowering enterprises to move from pilots to AI at scale with confidence." — Raj Koneru, Chief Executive Officer, Kore.ai Zensai is an AI-native software development company that ships its Human Success Agent to enterprise customers. Emma Taylor, Culture & Organizational Development Manager at Phoenix Software Solutions, one of Zensai’s customers, on what Agent 365 makes possible: "Zensai has given us a clear view of how our people and programs are performing, helping us track the metrics that matter. The depth of reporting across the Human Success Platform has been a game changer for our team. We're particularly excited about the Human Success Agent, with Agent 365 delivering the governance and observability our administrators need to confidently manage AI in the enterprise responsibly while surfacing the data and insights that drive better decisions across our business." — Emma Taylor, Culture & Organizational Development Manager, Phoenix Software Solutions The takeaway is direct: integrate once with Agent 365 SDK, and every customer who deploys your agent can easily enable enterprise-grade controls. Get started today The Agent 365 SDK is available now. If your agent is already running, you can onboard it in three steps. Install the SDK in your agent project using Python, TypeScript, or .NET. Register the agent with the Agent 365 CLI to provision its identity and automatically onboard it into Agent 365. Wrap your agent entry point with the SDK to stream activity and telemetry into the Agent 365 control plane. For data security visibility and controls, you can integrate Microsoft Purview APIs to enable capabilities such as prompt-based Data Loss Prevention (DLP), Data Security Posture Management, Insider Risk Management, and core compliance features including eDiscovery, Communication Compliance, Audit, and Data Lifecycle Management. Learn more in our Purview developer blog post. Get started with Agent 365 development Keep learning Microsoft is actively shaping the Agent 365 SDK based on what builders are asking for. A few places to go deeper and see the SDK in action: Watch OD840: The Microsoft Build on demand developer session that goes deeper on Agent 365 SDK and the design decisions behind it. Watch BRK251: Build secure and enterprise-ready agents with Agent 365. A hands-on breakout that walks through how Agent 365 SDK and Microsoft Purview APIs work together across the agent lifecycle, with practical examples for runtime visibility, identity-aware access, data protection, and policy-based governance. Available on Wed, Jun 3 11:30 AM - 12:15 PM PDT and on demand. Browse the docs: For quick-starts, reference, and the layered toolkit guide. Go deeper on Purview for agents: Start with the Purview developer blog for the story, then the Microsoft Purview developer documentation for the full reference. Read more on Entra Agent ID: Start with the Entra Agent ID developer blog, then the Microsoft Entra Agent ID documentation for the full reference. Shipping an agent that IT and security teams can actually approve doesn't have to mean piecing together multiple solutions. With the Agent 365 SDK, you can build enterprise-ready agents that organizations can deploy with confidence. Co-Authored by Jeremiah Follis
Word/PowerPoint are not suitable replacements for Publisher
I’m writing following the guidance that Word and PowerPoint can be used as replacements for Publisher. This feedback is based on completing a real production document, not theoretical use Having just completed a fairly complex, layout-heavy technical document, I thought it only fair to share how that works in practice. In theory, I can see the logic: Word handles documents PowerPoint handles layouts Therefore, between the two, everything should be covered Unfortunately, in reality, this appears to be more of a theoretical exercise than a practical solution. Publisher was clearly designed for: Fixed, page-based layouts Precise positioning of objects Efficient alignment of mixed content (text, images, tables) Producing consistent, professional multi-page documents By comparison: Word is admirably committed to reminding you that it would prefer everything to flow freely, regardless of whether you want it to or not PowerPoint, while better behaved, does seem to assume every page is a standalone slide rather than part of a structured document Both tools can, with enough persistence, be persuaded into doing the job. However, this involves a level of manual intervention, workaround, and general negotiation with the software that feels somewhat at odds with modern productivity software. To put it simply: They are not replacements in any meaningful, real-world sense. The end result can be achieved, but the process is unnecessarily time-consuming, fragile, and prone to unexpected layout changes—particularly when precision actually matters. Replacing a purpose-built publishing tool with two applications that were never designed for that role gives the impression that this use case has been… optimistically simplified. I would strongly encourage Microsoft to either: Provide a genuine page-layout solution within the Office suite, or Enhance existing applications so they can support fixed-layout publishing without constant workarounds At present, the gap left by Publisher is very noticeable for anyone producing structured documents beyond basic text. I appreciate the direction of Microsoft 365 overall, but in this particular area, the experience feels less like an evolution and more like working around a missing tool. Regards Andy
Please allow this foundational concept for algorithms
Hello dear friends of Excel. Please let me begin by thanking you all for giving us the excellent tool that Ms Excel is. I've being working practically my whole Computer Engineer career (~18 years) with this awesome tool, and I cannot imagine doing my work without it. It really is excellent, and has been enhancing a lot in the last years. In this occasion I would like to ask you to consider including in Excel, native support for "empty arrays", that is, arrays that have "0" (zero) items. This feature would help a lot in the following type of algorithms: When you have to scan a range of cells that hold the items of a set named "S", and from that set you have to select only the items that satisfy a given condition { ALL i | such that CONDITION(i) = TRUE }, and with those selected items (i) you have to construct a new vector named "V" In this case you usually need to begin with an "empty array", that is the initial value before adding any selected item, and at some point as you process the algorithm, maybe you will find the 1st. item to add to the "empty array" Maybe you won't find any item that satisfy the condition, and at the end of the algorithm, you will end up with an "empty array" as a result. To illustrate this type of algorithm, let me put an example: =LET( vector; SEQUENCE(10); new_vector; REDUCE( 0; vector; LAMBDA(building_vector;vector_i; IF(RESIDUO(vector_i;2)=1; VSTACK(building_vector; vector_i); building_vector ) ) ); INDEX(new_vector;SEQUENCE(ROWS(new_vector) - 1) + 1) ) This "algorithm", scans a set S = { 1, 2, 3, 4, 5, 6, 7, 8, 9, 10 } from S, it selects only the "odd numbers" { ALL i | such that "i is odd" }, it takes every odd number and adds it to the array named "building_vector", "building_vector" begins as a non-empty-array, holding "1 sentinel item" at the beginning of the algorithm (the number "0"), at the end of the algorithm, I have to do a work-around, to remove manually the 1st. sentinel item from the array The cons of this approach are: sometimes the resulting array will not have any selected item, that is, it will be an "empty array", and as such, Excel will generate an error showing #CALC! as Excel doesn't currently support empty arrays, I have to do this workaround to add an initial sentinel item at the beginning of the algorithm, and then I have to remember to remove it at the end of it Dear friends of Excel, I consider empty arrays to be a "foundational concept for algorithms". It's like the "zero" for numbers, but for arrays. It would be nice to be able to write this kind of algorithms with the aid of Excel, being able to natively support "empty arrays" without me having to do the extra work of handling a simulated situation of an empty array. I present you this request, and I ask you to please consider the importance of this feature. Thanks in advance!
Microsoft 365 Developer Program - Subscription Issue
I deleted my profile more than 60 days ago. Today, when I tried to create a new developer subscription, it turned out that the old one is still in the system even though it should have been deleted. I want to remove the old one and create a new one.
Excel can't open file from hyperlink after upgrade windows11
Hello, I met a strang issue. After upgrade system from w10 to w11, my excel can't open linkage file which was working normal before. Tested file and folder which located on local and SMB was not working, after click the hyper-lnik nothing happen and no pop-up just turn to mouse to loading icon then nothing happen how can I check which part cause this issue? Also tested on word have same issue. Further, url was working normal.Circular Reference Issues - A desperate woman needs help ASAP =(
I have an incredibly in-depth spreadsheet, with about 15 pages, and in-depth tables and calculations on most of those pages. Point being, I have a HUGE freaking file with tons of data collected over the years. Now, all of a sudden, I cannot input anything without the Microsoft Excel Warning popping up, stating: "There are one or more circular references where a formula refers to its own cell either directly or indirectly. This might cause them to calculate incorrectly. Try removing or changing these references, or moving the formulas to different cells." I understand what this pop up is saying, but my file is so huge, and there is so much information, I cannot find the error anywhere!!!!! And I don't have the option to search for it. So I cannot correct this error on my own, and I cannot input anything into the spreadsheet without having to exit out of that **bleep** pop up!!! I am defeated, INCREDIBLY FRUSTRATED, and I cannot see a clear path to recovery. I have been working on this document for years now, and I cannot start fresh. HELP, HELP, HELP!!!!!!!!!!!!! SOS!! Anyone! I am desperate and beyond frustrated =(Access fixes released in Version 2603 (Build 19822.20114)
Here's a summary of bug fixes in the latest version of Access: Bug Name Issue Fixed Edge Browser Control didn't navigate from code when inside a tab control When the Edge Browser control was hosted in a tab control, calls to the Navigate method from VBA succeeded, but the control didn’t refresh to show the new page. Switching tabs forced the refresh. The control now refreshes automatically after navigation, even when it’s hosted in a tab control. Some Unicode characters displayed incorrectly in Quick Import Certain extended Unicode characters were displayed as squares when importing data using Quick Import. These characters are now displayed correctly. Modern Chart titles truncated in Print Preview When viewing a report containing Modern Charts in Print Preview, chart titles might be truncated. Chart titles now render correctly in Print Preview. Some Unicode characters displayed incorrectly in exported object names When exporting an object whose name contained certain extended Unicode characters, the sheet name in the exported file displayed the characters incorrectly. These characters are now preserved correctly during export. Some Unicode characters displayed incorrectly in error messages for long object names When renaming a database object to a name that was too long, the error message displayed certain extended Unicode characters incorrectly. These characters now display correctly in error messages. Standard colors in Access didn't match other Office apps The standard color palette in Access used different color values than other Office applications like Word and Excel. For example, the standard red in Access was #ED1C24 instead of the updated Office standard red #EE0000. The color palette has been updated to match the rest of Office. Field.Properties("Precision") and Properties("Scale") on a query column caused the query to execute Accessing the Precision or Scale properties of a field in a query's Fields collection caused the query to execute. This was a regression that broke add-ins and code that enumerate field properties, since query execution can be expensive and have side effects. These properties are now returned without executing the query. Toggle filter button in status bar didn't work when no records were displayed When a form filter resulted in no matching records, clicking the Toggle Filter button in the status bar to remove the filter had no effect. The button now properly removes the filter even when the filtered result set is empty. PDF files with capitalized extension didn't render in Edge Browser Control When navigating to a PDF file using the Edge Browser control, if the file extension was capitalized (e.g., ".PDF" instead of ".pdf"), the file contents were rendered as raw text instead of as a formatted PDF document. The extension comparison is now case-insensitive. Monaco SQL editor inserted blank lines in multi-line comments When switching between Design View and SQL View, the Monaco SQL editor inserted blank lines between each line inside /* multi-line comment */ blocks. This affected both local and passthrough queries. The editor now preserves the original comment formatting. Please continue to let us know if this is helpful and share any feedback you have.
