Access and SharePoint Integration May Be Broken
I am posting this here in the hopes that a Microsoft MVP or employee may see it, verify the issue, and report it to the right people at Microsoft. We have a fairly significant LOB application with the front-end hosted in Access and the back-end hosted in SharePoint Online lists. This application has been working well for several years. Sometime in the past few weeks (last known good date was June 23), a change in either Access or SharePoint (or maybe the Windows OneDrive sync client) seems to have broken integration between the products. When the modern cache format is enabled (the default), all SharePoint calculated columns unexpectedly show errors, as shown here (in a fresh database where I imported just one list from our site as a test): Naturally, this completely borks the application, with VB code throwing errors at startup. Using the legacy cache format, or disabling caching altogether, seems to restore functionality--(though this would come at a cost to performance): But there is a major caveat to this. Other functionality is apparently broken. We have straightforward update queries, for example, the hang indefinitely in these modes, rendering this an unacceptable work-around. I have been able to replicate this on several different PCs. Also, on several different SharePoint sites in our tenant. Currently, this is blocking work for us, and we are hoping to see it resolved as soon as possible. If anyone with knowledge of the right people at Microsoft to call attention to this, we would be grateful for any help. I am using the Access forum because the last time I tried to get help from SharePoint Online support for an Access-related query issue using SP list data, they had no idea what I was talking about. (Also, for Access database experts: please do not suggest that we avoid using calculated columns in SharePoint lists. This is a hybrid app with most of our users working with data strictly through SharePoint, and SharePoint views do not support the same features as queries do in Access. Making use of these SharePoint features are essential for these users.) Our Access version: Microsoft® Access® for Microsoft 365 MSO (Version 2607 Build 16.0.20228.20124) 64-bit Thank you in advance for any help.
SPMT Error help
I am migrating from SP2019 on-prim to SPO using SPMT tool. I have 2 libraries that are failing with errors below. Errors or timeout for Server Processing the file:There isn't enough disk space in the target site collection. Errors or timeout for Server Processing the file:Not all the items in the package have been migrated There is plenty of space on the destination site collection. Any ideas on what can be causing this issue and how to resolve?AutoSave disabled when opening SharePoint-synced files from Finder after macOS Tahoe 26.6 update
Files stored in SharePoint Online and synchronized locally through OneDrive are opened as local documents when launched from Finder. Office applications display "Saved to my Mac" and AutoSave is turned off by default. However, opening the exact same files through Word/Excel > Open > Sites, or via SharePoint "Open in Desktop App", correctly identifies them as cloud documents. In that scenario, AutoSave is enabled and collaboration/version history features work as expected. Troubleshooting already performed: OneDrive reset and re-linked SharePoint library re-synced Signed out and back into both Office and OneDrive Removed Microsoft credentials from macOS Keychain and re-authenticated Recreated local OneDrive sync relationships Verified OneDrive File Provider extensions are enabled Verified Office applications and OneDrive are fully up to date Tested with newly created files and existing files Tested "Always Keep on This Device" with no change in behavior The issue appears to be specific to the Finder-to-Office launch path after upgrading to macOS Tahoe 26.6. Before upgrading to macOS Tahoe 26.6, opening the same SharePoint-synchronized files directly from Finder correctly preserved cloud document identity and AutoSave was enabled as expected. I discussed this issue in detail with Apple Support, but they quickly dismissed it, saying that the problem is not on Apple's side and that I should contact Microsoft instead.Restricted Content Discovery Gets a Makeover
Restricted Content Discovery (RCD) is an important guardrail for Microsoft 365 Copilot deployments. Microsoft is tightening how RCD works to eliminate a corner case where recently accessed files from protected SharePoint Online sites could still surface in Microsoft Search and become available to Copilot. The update closes that loophole by ensuring that recently accessed files from RCD-enabled sites remain hidden from Search and Copilot. https://office365itpros.com/2026/08/05/restricted-content-discovery-2/
Converting string type to person group field type in Sharepoint
Hello everyone, I have task to build a flow which will be adding and updating Items in sharepoint list from excel file. I have a issue due to converting string type from Excel (name) to a person field type in sharepoint list. Is it possible to do that? I didn’t find any solution that would help. I would be greatful for any hints and solutions ☺️
A new SharePoint Look and Feel: What’s Changing and Why It Matters
SharePoint is getting a refreshed look and feel designed to make the product feel simpler, clearer, and more focused on your content. We’ve recently introduced a new SharePoint experience, organized around helping you discover knowledge, publish content, and build solutions. Along with that new experience, we’re introducing visual updates across key product surfaces that reduce visual noise, improve readability, and bring more consistency to the interface while preserving the branding investments your organization has already made. We call this work the SharePoint visual refresh: a thoughtful update to the product’s visual language that helps SharePoint feel more modern, approachable, and easier to use. Background Over time, SharePoint’s capabilities have continued to grow, which has given us an opportunity to update the look and feel as well. These updates not only make the SharePoint UI fresh, but it ensures that we are consistent across M365. The SharePoint visual refresh, rolling out to general availability now, is part of a broader collaborative effort across Microsoft 365 to modernize the suite and improve usability with this bold, new visual design, while also responding to customer feedback about visual clutter and the need for clearer focus on content. These updates are grounded in core design principles that prioritize usability, coherence, and a sense of delight in everyday interactions. This bold, new design is part of a larger update across many apps (such as Microsoft 365 Copilot) and platforms that family together to create a cohesive, modern look and feel. Goals The Visual Refresh is guided by several key goals: Deliver a more contemporary, polished look aligned with the broader Microsoft 365 experience to existing and new SharePoint experiences Improve consistency, usability, and accessibility across key SharePoint surfaces, including Sites, Pages, and Document Libraries and the new Discover, Publish, Build destinations. Reduce visual clutter to improve focus on what matters most: your content Create a design system that scales, from simple team sites to complex enterprise scenarios Consistency Across Experiences Once adopted, the visual refresh will strengthen alignment between SharePoint, OneDrive, Teams and the Microsoft 365 shell, reducing visual fragmentation across navigation, pages, and components. By aligning how our UI looks and our theming approaches, we aim to create a more predictable experience for users moving between tools and surfaces, helping avoid visual dissonance and reducing cognitive load across day‑to‑day workflows. What’s being updated Canvas elevation: putting content in the spotlight One of the most noticeable changes is the elevation of the SharePoint site canvas. By adding a subtle shadow, refined spacing, and a light gray shade to backgrounds, the refreshed design helps your content stand out, making it easier to scan, read, and interact with pages. Importantly, this is not achieved by changing your content. Instead, the improvements come from thoughtful adjustments to padding, layout spacing, and visual framing, ensuring that the emphasis remains on the information you create and manage. This does not effect existing layouts or how sites reflow. Neutral theming for app surfaces We’re also evolving how themes are applied within SharePoint to improve consistency, accessibility, and clarity across experiences by separating the core SharePoint user interface from customer content. Updated neutral theming of app surfaces provides a more stable visual foundation and establishes a unified set of navigational UI, where the customer brand remains in an anchor position and is in harmony with the new neutral navigation. This approach allows customer branding to be expressed more clearly without competing with structural UI elements, clarifies the distinction between customer branding and the SharePoint app, reduces visual competition, and improves focus on primary content. ual noise, improving usability. Styling updates Additional updates to typography, spacing, and corner rounding introduce a more cohesive and contemporary visual language across SharePoint surfaces. Updated typography and spacing enhance readability and create more consistent rhythm across pages and components, making information easier to scan and interact with. At the same time, increasing corner radius of the UI makes it feel more approachable, and through a flexible system brings greater consistency to our products, helping related components feel more integrated and visually connected. Together, these refinements simplify the overall interface, reduce unnecessary visual noise, and contribute to a lighter, more modern experience that aligns more closely with the broader Microsoft 365 design ecosystem. What’s Not Changing While the visual refresh introduces meaningful visual improvements, core SharePoint concepts and workflows remain familiar. Your content, structure, and brand are preserved Existing site architecture remains unchanged Day‑to‑day workflows continue to work unchanged There is no impact on existing SPFx extensions or solutions with this change This update focuses on evolution, not reinvention, so users can benefit from improved clarity and modern visuals while familiar work flows and patterns remain the same. Evaluated with Research Across our research studies, participants consistently favored the Visual Refresh due to the cleaner and more contemporary look and improved labeling and structure. A calmer, more modern UI that’s easier to scan. Elevation + neutral theming made the page feel cleaner and it is easier to focus on the content. Clearer actions in the command bar. Stronger affordances (like button outlines) make common tasks - edit, undo, save, share - more obvious and easier complete workflows. Less guesswork when navigating. Icons and labelling in the app bar reduced friction and participants spent less time hovering and interpreting icons, especially those less familiar with SharePoint. Overall, the Visual Refresh provides users with a new look they prefer without slowing down their workflow. Looking Ahead The SharePoint Visual Refresh is part of an ongoing journey. We’ll continue refining the experience, learning from customer feedback provided directly in-product, and shipping improvements incrementally, so SharePoint keeps getting better without disrupting how people work. Familiar workflows will remain in place, now enhanced by improved clarity, consistency, and a more modern feel. We welcome all feedback! See this post for more information about SharePoint’s exciting next chapter.
Extreamly frustrated that I cannot get help for a serious problem
What the devil do I have to do to get help with a serious problem with the cloud for our non-profit business account for our small charity. I have 'lost' sight of a large number of documents from the cloud since we had to start paying for our subscription. After many chats with ai and emails and the problem being escalated I have now been told to go back to where I started at Non-profit support and put a support ticket in. Doesnt matter what machine I use, what browser I use, what network I use, I cannot get past the submit form page and keep getting an error message - this has been going on for weeks now. Ive tried ringing and the call keeps dropping while on hold - no one, no-one will call me about the problem and no one seems interested in dealing with the problem and its not just affecting me on our system either. Please will someone tell me how to get to a human for support without using an AI help system,SharePoint Showcase: 10 Custom AI Skills Every SharePoint Site Owner Should Build
In this edition of SharePoint Showcase, we explore how skills work, how to create or install them, and ten practical examples to help SharePoint site owners get started. These examples are not an exhaustive list, but a curated starting point for identifying everyday processes that can become reusable, team-ready skills.Web invoke in power automate says unauthorized but can browse from browser
I am able to browse to this url directly from browser https://my365.crm9.dynamics.com/api/data/v9.2/audits?$filter=objecttypecode%20eq%20%27myissuetable%27%20and%20_objectid_value%20eq%20%271de46d6b-b986-f111-ab0e-001dd80b339b%27&$select=_objectid_value,objecttypecode,changedata,createdon,_userid_value but when i use the invoke http from power automate it says unauthorized. i am using the same account. What is the issue is there anything i need to do so that it works?Which SharePoint Communication Site layout has worked best in your organization?
Hi everyone, We're redesigning our SharePoint Online communication site and comparing different homepage layouts for HR, IT, Finance, and Corporate Communications. I'd like to hear from the community: Which homepage layout has worked best in your organization? Which web parts do you consider essential? Have you found any design patterns that significantly improved user adoption? Looking forward to learning from your experiences and recommendations.
