microsoft365
312 TopicsSharePoint File Attachment Access with OWA
When using Outlook Web Access, we're unable to see our SharePoint Team site when we try to attach a file from the SharePoint site. The SharePoint site is a Team site (classic experience). Is there a way to enable SharePoint as an available location when using the standard paperclip attachment option with OWA? Thanks for any input or suggestions.66Views0likes2CommentsNew SharePoint Site Creation Controls: A Better Approach to Site Governance
Managing SharePoint site creation is one of those topics that quickly becomes important as a Microsoft 365 environment grows. The challenge is familiar: organizations want to enable self-service, but they also want sites to follow internal governance, naming, ownership, lifecycle, and provisioning requirements. Microsoft is improving this experience by giving SharePoint administrators more control over what happens when users try to create a new site. One particularly useful option is the ability to redirect users to an organization-approved site request process. Instead of relying only on the standard SharePoint site creation experience, administrators can direct users toward their own provisioning solution or request page. This enables scenarios such as: ✅ Request and approval workflows ✅ Custom site provisioning processes ✅ Naming and governance policies ✅ Additional metadata collection ✅ Business justification or ownership checks ✅ Automated provisioning with Power Automate or other solutions Where is the setting? Administrators can find the configuration in: SharePoint Admin Center → Settings → Site creation From there, organizations can decide how the SharePoint site creation experience should work and whether users should be redirected to an approved request process. One important consideration SharePoint site creation is only part of the overall Microsoft 365 provisioning story. Organizations should also consider how Microsoft 365 Groups and Microsoft Teams are created because these workloads can also result in connected SharePoint sites. So, if your goal is comprehensive governance, your strategy should look beyond only the SharePoint Create site experience. 🎥 I created a step-by-step video showing the configuration and how the new experience works: I'm curious how other organizations are approaching this. Do you allow completely open SharePoint site creation, use a request/approval process, or have an automated provisioning solution? Share your approach in the comments. It would be great to compare how different organizations are tackling this. #SharePoint #Microsoft365 #SharePointOnline #Governance #Microsoft365Administration49Views0likes0CommentsFailed to load current time zone
SharePoint List Fails to Save Items After Changing Site Time Zone to "Pacific Time (British Columbia)" British Columbia will move to permanent Daylight Saving Time effective November 1, 2026. As a result, clocks will no longer fall back by one hour and will remain on UTC-07:00 year-round. Microsoft has introduced the new time zone (UTC-07:00) Pacific Time (British Columbia) for this change. As part of this transition, we updated the site's Regional Settings from (UTC-08:00) Pacific Time (Canada/US) to (UTC-07:00) Pacific Time (British Columbia). We have SharePoint lists with Start Date & Time and End Date & Time columns configured as Date and Time fields in multiple sites. Following this change, one specific site is now experiencing an issue where both users and site administrators are unable to save list items. The following error is displayed: "Failed to load current time zone" Additional Details: The issue started immediately after changing the site's Regional Settings. Reverting the site back to Pacific Time (Canada/US) did not resolve the issue. Some other SharePoint sites were updated to the same Pacific Time (British Columbia) setting and continue to work correctly. The affected site contains a calendar view built on a custom SharePoint list. The Start Date and End Date columns are configured as Date/Time fields. Location: Victoria, British Columbia. Has anyone encountered this issue before? Are there any known dependencies related to Regional Settings, Date/Time columns, calendar views, or site time zone configuration that could cause this behavior on a single site while others continue to function normally? Any guidance would be appreciated.Solved461Views1like6CommentsSharePoint News Email “Content too large” issue – size limit clarification
Hi, We are currently trying to send a SharePoint News post via email and encountering the following error: “The contents of this page are too big to send in email.” We performed testing to understand the limitation and observed the following: Full newsletter (~5.29 MB) → ❌ Error Pages 1–12 (~3.11 MB) → ❌ Error Pages 1–11 (~2.80 MB) → ✅ Works Slight increase (~2.90 MB) → ❌ Error again ✅ Based on testing: Practical threshold seems around ~2.7–2.8 MB Above this, email rendering fails ❓ Questions: Is there a documented maximum size limit for SharePoint News email content? Is the limit based on: Total content size after rendering? Image count/size? Can this limit be configured or increased? What are the recommended best practices for image-heavy newsletters? ✅ Current understanding: It appears that the limitation is due to HTML email rendering size rather than just file size Any clarification or official guidance would be appreciated. Thanks.516Views1like2CommentsOneDrive & SharePoint Online inaccessible after subscription transition
I have used OneDrive for Business for almost 10 years. Following a billing interruption and migration to Microsoft 365 Business Standard, both OneDrive and SharePoint Online became inaccessible. Despite five support tickets and multiple troubleshooting sessions, the issue remains unresolved. I am hoping the community or a Microsoft engineer can help identify the root cause. BACKGROUND: My legacy OneDrive for Business subscription experienced a payment interruption due to an expired credit card. Following Microsoft's Support team's instructions, I paid the outstanding invoice by wire transfer. Microsoft Billing Support confirmed receipt by email, although the payment is not appearing in the Admin Center, explained that was normal. Following Microsoft's Support team's instructions, I subsequently subscribed to Microsoft 365 Business Standard under the same tenant and existing user account. The affected user has valid, active licenses, but access remains blocked. CURRENT SYMPTOMS: OneDrive fails to retrieve its configuration. OneDrive personal site (my.sharepoint.com) is inaccessible. Business files remain inaccessible. TROUBLESHOOTING COMPLETED: Multiple Microsoft Support calls and screen-sharing sessions. Browser/cache/cookie troubleshooting. License reassignment, disable/enable Billing and payment restrictions verification. None resolved the issue. SUPPORT HISTORY: Five tickets raised, including #2611031420001514 and #2610301420001454. Repeated escalation requests without resolution. NEED HELP : Has anyone experienced a similar issue after a subscription transition? Are there tenant-level diagnostics to identify lingering service restrictions or provisioning inconsistencies? Could the legacy subscription's suspended or restricted service state still be affecting SharePoint/OneDrive provisioning, despite the new active Microsoft 365 licenses? I would especially appreciate assistance from a Microsoft engineer or moderator in escalating this for backend investigation. Thank you for any guidance.155Views0likes2CommentsSharePoint Migration Tool after failed copying
Hi, a user tried to migrate a local storage to SharePoint Online. He set up a sync between his Windows Explorer and the SharePoint library and did a plain copy of all folders & files from the network storage to the synced library. Now not all files or folders arrived on SharePoint but he already started to worked in the synced folder. Can I re-migrate fromn the network drive to SharePoint with the SPMT and keep the newer versions of the files? If so, how do I have to set up the SPMT? Thx and best regards1.2KViews1like6CommentsSupported App-Only APIs for SharePoint Site Access and Group Membership (No PowerShell)?
a { text-decoration: none; color: #464feb; } tr th, tr td { border: 1px solid #e6e6e6; } tr th { background-color: #f5f5f5; } I am trying to determine the supported approach for retrieving SharePoint Site Owners, Members, and Visitors (effective user access) in an App-Only (Application Permissions) scenario without using PowerShell. Specifically, I am building an MCP tool that needs to: Check whether a specific user has access to a particular SharePoint site. Retrieve the list of users who have access to a SharePoint site, especially through the SharePoint Owners, Members, and Visitors groups. From my understanding, Microsoft Graph can be used to enumerate SharePoint sites and permissions, but retrieving the actual membership of the associated SharePoint groups does not appear to be fully supported through Graph alone. Most recommendations I have found suggest using SharePoint REST APIs, CSOM, or PnP-based solutions. My questions are: How can I retrieve SharePoint Site Owners, Members, and Visitors (effective user access) in an App-Only scenario without using PowerShell? Are there any supported Microsoft Graph APIs (including Beta APIs), SharePoint REST APIs, SDKs, Python libraries, CSOM, or other approaches that can provide this information? Can a backend service implemented entirely in code (without PowerShell execution) determine: Whether a specific user has access to a SharePoint site? The users belonging to the site's Owners, Members, and Visitors groups? The reason for asking is that I am developing a backend service, and invoking PowerShell from the application is not a practical option. I am looking for a supported API/SDK-based solution that can be implemented directly in code using App Registration permissions only.300Views1like2CommentsMicrosoft Foundry Guardrails Getting in Your Way? Here’s How to Dial Them Down
How This All Started So here’s the story. I just got back from a trip and had a pile of footage sitting on my laptop. Being the lazy (sorry, efficient) person I am, I fired up OpenCode and asked GPT-6 Astra, running on Microsoft Foundry, to cut me a travelogue. Nothing fancy: under two minutes, nice lighting, clean transitions, no cringy effects, a quick QA before showing me, and the output in its own folder. Easy, right? Nope. This is what I got instead: “Image processing blocked due to content policy violation.” Seriously? It’s holiday footage! Nothing even remotely dodgy in there. This is a classic false positive from the default guardrails, and the good news is it’s totally fixable. Let me show you how. My Setup Quick context before we dive in: I’ve got two models deployed on Microsoft Foundry, gpt-6-astra and gpt-6-sol. Both were running on Microsoft’s out-of-the-box guardrail. Step 1: Find the Guardrails Page Head over to the Microsoft Foundry portal, click Build, then hit Guardrails in the left menu. You’ll see three guardrails that Microsoft gives you by default: Microsoft.Default, Microsoft.DefaultV2 and Microsoft.MAIDefault. Microsoft.DefaultV2 is the one every new deployment gets, which is why it’s sitting on both of my models. Here’s the catch: you can’t edit or delete these Microsoft-managed defaults. So instead of tweaking them, we’re going to build our own guardrail and swap it in. Step 2: Create Your Own Guardrail Smash that "Create" button and you’ll land on the Create guardrail page. This is where all the knobs and switches live: Every control has three bits: the risk type, the intervention point (does it check what you send in, what the model spits out, or both?) and the action. The magic trick for loosening things up is flipping the action from Block to Annotate. With Annotate, Foundry still scans the content and tags it in the API response, but it stops slamming the door on your request. So What Does Each Setting Actually Do? Before you go on a switching-off spree, it’s worth knowing what each of these does and what you’re giving up when you loosen it. Here’s the quick tour: Jailbreak: This one catches prompts trying to trick the model into ignoring its rules. On Block, those prompts get rejected outright. On Annotate, they go through with a flag. Turn it off completely and you’re trusting the model’s own training to keep it in line. Network (egress rules): Controls which outbound calls a hosted agent is allowed to make. As the portal points out, it only applies to hosted agents, so for plain model deployments like mine it doesn’t change a thing. Indirect prompt injections: Watches user input and tool responses (files, docs, web pages the model reads) for sneaky instructions someone has planted. Leave it on and your agents are protected when they read outside content; switch it off and a dodgy file could quietly hijack your model. For an agentic tool like OpenCode, which reads files and runs shell commands, I’d honestly keep this one on, even if it’s just on Annotate. Spotlighting (Preview): Tags external content inside the prompt so the model can tell your real instructions apart from random untrusted data. Think of it as an extra seatbelt against indirect attacks. Content harms (Hate, Sexual, Self-harm, Violence): Each of these has a severity slider that starts at Medium blocking, meaning anything rated medium or higher gets blocked. Slide it down to Lowest blocking and only the really nasty stuff gets stopped, which kills off most false positives like mine. The asterisk means these four are mandatory: you can turn the dial down, but you can’t switch them off. Blocklists: Want to ban specific words or phrases, like profanity or your competitor’s name? This is where you do it. It’s off by default. Protected material for code and text: Checks whether the model is about to spit out known copyrighted text (song lyrics, articles and so on) or code lifted from public repos. Block stops it; Annotate lets it through with a flag. Switch it off and you’re rolling the dice on your app reproducing someone else’s copyrighted work. Step 3: Pick Your Models Hit Next and Foundry asks which agents and models you want this guardrail on. Any model you’ve already deployed in your project shows up here. For me that’s gpt-6-astra and gpt-6-sol, so I ticked both. Step 4: Name It and Pick a Streaming Mode One more Next and you’re on the Review page. Give your guardrail a name (I went with NoGuardrails, because subtlety isn’t my thing) and pick a streaming mode. You’ve got two choices: Default: Foundry buffers the response and runs it through the guardrail before each chunk goes out. Nothing reaches the user until it’s been checked. Safest option, but you’ll feel a bit of lag when streaming. Asynchronous: Content streams back the moment it’s generated, with the filters running in the background. Much snappier, but flagged content might flash up briefly before the filter catches it, so your app has to clean up after the fact. Microsoft pitches this for low-latency stuff like internal dev tools, which is exactly my use case. Give the summary a quick once-over, then click Create. Done! Did It Work? Yep! With my shiny new guardrail in place, I fired off the exact same request, this time to GPT-6 Sol. And boom: no more content policy error. The model went straight to work scanning my footage and putting the video together. Wrapping Up Look, Microsoft’s default guardrails are a solid starting point, but they can be a bit trigger-happy when you’re doing perfectly legit stuff like video editing, creative work or internal tooling. Since you can’t touch the defaults, the trick is to roll your own: flip Block to Annotate where it makes sense, drag those content harm sliders down, pick the streaming mode that fits your app, and assign it to your deployments. That’s it! One friendly word of warning though: with great power comes great responsibility. Only loosen what you actually need, keep things like indirect prompt injection detection switched on for any agent that reads files or browses the web, and think twice before doing this on anything customer-facing. And if you want to go further than the portal lets you, like switching content filters off completely, you’ll need to apply to Microsoft for approval first. Happy building!572Views1like2CommentsApplying Search Schema fails
Hi everyone, We've been fighting a SharePoint Online search issue at one of our customers since early July 2026. We've had a Microsoft Support case open for a few months, but it has hit a dead end. I'm posting here to find out whether others are seeing the same thing and whether anyone has found a workaround. Our setup An in-house ERP system syncs customers and projects to a SharePoint list, which serves as the provisioning master list. A provisioning engine (PnP PowerShell / PnP provisioning templates) creates a site for each item, using one of two templates: Customer site or Project site. During provisioning we apply: Property bag values at site level (for example, the account manager for a customer) Custom columns in the document libraries for document metadata SearchSettings in the XML template that map both the property bags and the columns to the default RefinableStringXX managed properties Some values link to managed metadata, and some are free text. This approach was designed together with the customer, and Microsoft Support confirmed that it is a supported implementation. The issue Applying the SearchSettings fails. Running Invoke-PnPSiteTemplate with the SearchSettings section returns one of these: Service unavailable now, please try again later. The request was canceled due to the configured HttpClient.Timeout of 100 seconds elapsing. Without SearchSettings, the template applies without problems. Even applying only the first line of the SearchSettings on a brand-new site causes the timeout. The Search Schema pages are extremely slow at both site collection and tenant level, much slower than in any other tenant we work in. The issue has now gotten worse. We can't create, modify or delete any managed property mapping, at either site collection or tenant level. Opening _layouts/15/selectcrawledproperty.aspx (for example, to edit RefinableString01) now always returns "Sorry, something went wrong. An unexpected error has occurred." What Microsoft Support told us At first, the case was pushed back as out of scope because we use PnP. After escalation, engineering confirmed that the behaviour matches a known issue: Search Schema pages load slowly when a large number of implicit properties and mappings exist. They confirmed it's not caused by misconfiguration on our side. However, there is no public documentation, no workaround, no fix and no ETA, and no further escalation path. They suggested we give feedback through the community, so here we are. Questions for the community Has anyone else run into this Search Schema latency or the "Service unavailable" error when applying SearchSettings, especially in tenants with many sites and mappings? Has anyone been able to reduce the number of implicit or crawled properties in a tenant, or "reset" the site-level search configuration, and did that help? Could this be related to the recent search migration issues reported in service health SP1393483 and in this thread? Are there any best practices or (unofficial) limits for the number of property bag values or library columns mapped to RefinableStrings across many sites? For example, does linking to managed metadata make it better or worse? Has anyone tried splitting the SearchSettings into smaller increments and applying them one by one? We're also looking at reducing the number of mappings and the number of sites that need search support. Still, it would be very helpful to understand the actual limit we're hitting, since this affects how we design future solutions as well. Thanks in advance for any insights!501Views0likes4CommentsAbility to schedule email of SharePoint post
We've started using SharePoint to create and send mass emails in our organization, but its a huge pain that I can't schedule them ahead of time to send at a specific time/date. Could you work on creating a way to schedule not just the publishing of a SharePoint news post, but when it is shared via email? That would be amazing.309Views1like3Comments