Forum Widgets
Latest Discussions
Navigating SharePoint App Permissions After Azure ACS Retirement
With the retirement of Azure ACS (Access Control Services), the familiar SharePoint page (_layouts/15/appprincipals.aspx) used to view and manage app permissions is no longer available. Previously, developers could quickly inspect and revoke app permissions directly from this interface. Now, permission management has shifted to more modern approaches using Azure AD app registrations and SharePoint Online PowerShell. To review and remove permissions, developers should leverage tools like the Microsoft Graph API, Azure Portal (for Enterprise Applications and App Registrations), or SharePoint Online Management Shell (Get-SPOSite, Get-SPOAppPrincipal, and related cmdlets). This transition encourages better alignment with current security practices, centralized identity management, and improved governance across Microsoft 365 environments.
SPFx CDN URLs not consistently added to Trusted Script Sources (CSP)
Hi everyone, We’re currently investigating an issue related to SharePoint Online Content Security Policy (CSP) and Trusted Script Sources (TSS) for SPFx solutions. [SharePoint Online] [SPFx] [CSP] Scenario We deployed multiple SPFx .sppkg packages via App Catalog These solutions load scripts from an external CDN (cdnBasePath, with includeClientSideAssets: false) Expected Behavior As per documentation, CDN URLs used by SPFx solutions should be available/registered in Trusted Script Sources so that scripts can load under CSP enforcement Observed Behavior Only some CDN URLs (from certain packages) appear in Trusted Script Sources Others are missing, even though they are similarly configured and deployed Due to this, scripts from those missing sources are blocked by CSP, and the extension fails to load Additional Notes No use of eval() or inline scripts in our code Re-deploying packages sometimes resolves the issue (CDN URLs get registered afterward) Behavior appears inconsistent across environments Question Has anyone encountered a similar issue where: Trusted Script Sources were partially auto-populated from App Catalog deployments? CDN URLs from some SPFx packages were not registered automatically? Any insights on: Root cause Known limitations Best practices to ensure consistent registration would be really helpful. Thanks in advance!
Post SPFX webpart deployment - JS conflictings
Hi, I am working on the Classic SharePoint Online project. I need to migrate the Provider hosted apps to SPFX. Most of the functionality has been implemented using HTML and Javascript. Using Javascript Provided hosted app methods are being called directly on SharePoint Page. Huge client side scripts are written. I have migrated all the provider hosted apps code to Asp.net web api and deployed in Azure. I have configured Azure AD authentication on top. I am using SPFX webpart which is consuming the APIs and returning the values. SPFX methods are exposed to be accessible via external js. I deployed the SPX app in Sharepoint classic pages. Some Page it is working fine. On some webpart it experiencing error : Something went wrong If the problem persists, contact the site administrator and give them the information in Technical Details. Technical Details I checked in browser console seeing error : Error: Mismatched anonymous define() module: function(){return A} https://requirejs.org/docs/errors…, stage: 'Load'} requireModules: undefined requireType: "mismatch" message: "Mismatched anonymous define() module: function(){return A}\nhttps://requirejs.org/docs/errors.html#mismatch" stack: "Error: Mismatched anonymous define() module: function(){return A}\nhttps://requirejs.org/docs/errors.html#mismatch\n at makeError (eval at e [[Prototype]]: Object error: Error: Mismatched anonymous define() module: function(){return A} https://requirejs.org/docs/errors.html#mismatch at makeError (eval at e stage: "Load" [[Prototype]]: Object How can i fix it? Please help. Thanks in advance. AK
Central News Help
Hello everyone, I’m looking for guidance on using SharePoint to distribute department updates across multiple locations, with an administrator controlling who sees each update. Our organization uses a dedicated Microsoft Team for each location (27 total). A single update may need to be shared with one location, several locations, or all 27. Conceptually, I have a solid understanding of how this should work, but I’ve run into some practical roadblocks, and Copilot hasn’t quite gotten me where I need to be. Here’s the workflow I’m envisioning: A Department Head submits an update via a Microsoft Form. The form responses are stored in a SharePoint List on a central “News Hub” site. An Admin reviews the submission, makes edits if necessary, selects one or more target locations, and publishes the update. Each update includes a publish date and an expiration date, since these updates are used for monthly meetings at each location. Based on the selected target locations, the update would either: Display on a SharePoint site associated with the corresponding Team(s), or Remain on a centralized News Hub as an additional page that can be embedded on a TEAM channel. The page itself would contain both static content and dynamic monthly updates. The updates should be visible as text only (not clickable), as I want managers to see the information without navigating away from the page. The final output would be embedded into a Teams channel, allowing each location’s manager to see only the updates targeted to their specific office. From my understanding, this aligns with a “hub-and-spoke” news model, using: Microsoft Forms SharePoint Lists Power Automate (triggered when a list item is modified) Logic to route or display updates to the appropriate locations I’d prefer to avoid building a Power App if possible, but I’m open to it if that’s the only viable solution. Also, I have complete rights to the Central News Hub and the Sharepoint and Team site that I am testing on. Any advice, best practices, or examples of similar implementations would be greatly appreciated. Thank you in advance.
Visualizing SharePoint List Relationships as ER Diagrams
In several SharePoint-based projects, I encountered the same challenge. As solutions grow, list relationships become increasingly difficult to understand. This is especially true in environments with multiple lookup columns, implicit relational structures, and long-lived tenant environments where schemas evolve over time. Although SharePoint provides rich metadata, there is no built-in way to visualize list relationships as an ER diagram. To explore this problem, I built a small browser extension that extracts list and column metadata from a SharePoint site, detects lookup relationships, and generates PlantUML-based ER diagram code. It can also export structured definitions to Excel. The goal is not only diagram generation, but improving architectural visibility, impact analysis during schema changes, documentation quality in long-term projects, and migration planning such as moving SharePoint lists to Dataverse. I am particularly interested in how other developers document SharePoint list structures in larger environments. The extension itself is available here: https://chromewebstore.google.com/detail/sharepoint-erd-generator/nbjfcilmndpofckndmcadgfcacadgeak I would appreciate any feedback or discussion around approaches to SharePoint schema documentation.Viva Learning – SharePoint content provider configured but content not appearing in Teams
Hi everyone, I’m configuring Viva Learning in Microsoft Teams and I’m trying to use SharePoint as a content provider to publish custom learning content (Word, PowerPoint, Excel, PDF, audio, video, and web links). What I’ve done so far: Created a dedicated SharePoint site. Waited about one hour before adding it as a SharePoint provider in Viva Learning. After the configuration, the “Learning App Content Repository” list was automatically created. In the document library, I uploaded: PDF files a web link I copied the folder URLs and added them to the Learning App Content Repository list. I also followed the official procedure to create and assign a Microsoft 365 Group, as described in this documentation: https://learn.microsoft.com/en-us/viva/learning/sharepoint-permissions The issue: Almost 24 hours have passed, but I still don’t see any content in Viva Learning (Teams). In the sync logs, I can see that synchronization jobs are running, but the content is either not appearing or only partially synchronized. At this point, I’m not sure: if I’m missing something in the SharePoint provider configuration, if the folder URLs are incorrect, or if there’s some additional requirement related to permissions or metadata. Has anyone experienced a similar issue or can suggest what I should check next? Thanks in advance!
Group Calendar Web Part Pop Up Color
We have created a branding theme for modern sharepoint sites to match corporate colors. When clinking on a Group Calendar event, the pop up now applies a background color we didn't have in the theme as primary or secondary. Just seems to be auto selected by SP. It's too dark to read the text. I've found the Them in the classic _catalog Theme Gallery and can pull the theme into NotePad to read it but can't seem to tell which variable controls the background of pop ups. Just need it to be white (ffffff). Anyone have a solution? {"name":"(Company Theme Name)","isInverted":false,"palette":{"themeDarker":"#243360","themePrimary":"#17244C","themeSecondary":"#5e6d9b","themeTertiary":"#7885af","themeLight":"#94a0c2","themeLighter":"#b3bcd6","themeLighterAlt":"#d6dbea","black":"#000000","neutralDark":"#201f1e","neutralPrimary":"#323130","neutralPrimaryAlt":"#3b3a39","neutralSecondary":"#605e5c","neutralTertiary":"#a19f9d","neutralTertiaryAlt":"#c8c8c8","neutralLight":"#eaeaea","neutralLighter":"#f4f4f4","neutralLighterAlt":"#f8f8f8","white":"#ffffff","neutralQuaternaryAlt":"#dadada","neutralQuaternary":"#d0d0d0"},"displayMode":"light","secondaryColors":{"light":[{"themePrimary":"#ffffff","backgroundColor":"#17244C"},{"themePrimary":"#6BC289"},{"themePrimary":"#ffffff","backgroundColor":"#6BC289"},{"themePrimary":"#26A9E1"},{"themePrimary":"#ffffff","backgroundColor":"#26A9E1"},{"themePrimary":"#1B75BC"},{"themePrimary":"#ffffff","backgroundColor":"#1B75BC"},{"themePrimary":"#E7EBF6"},{"themePrimary":"#ffffff","backgroundColor":"#E7EBF6"},{"themePrimary":"#ACBFE3"},{"themePrimary":"#ffffff","backgroundColor":"#ACBFE3"},{"themePrimary":"#B6BBBF"},{"themePrimary":"#ffffff","backgroundColor":"#B6BBBF"}],"dark":[]}}Size increase of .sppkg packages with heft/v1.22
After upgrading our solution to SPFx 1.22.rc-0 and switching to the new heft build toolchain our .sppkg packages have suddenly grown massively in size. They are more than double the size of the 1.21 version. Is there a reason for this? Is there anything we can do to reduce the package size back to what it was previously? Our main solution contains both web parts and list extensions, split into several bundles. Let me know what other details would be helpful.
Is Creating Multiple ClientContext Instances Efficient in CSOM for one Site Url?
Is it efficient to create a new ClientContext for each site URL and for each query, such as getting site users, lists, groups, and group members from the Web object? These queries can return a very large number of items, and CSOM does not support paging when retrieving data from Web properties. Because of this, there is a risk of memory issues. In this case, is creating multiple ClientContext objects a good approach? Also, how does ClientContext work internally, and how does it handle memory and performance?
SharePoint Online SP.FieldUserValue.get_email() always returns NULL.
Since last week, SP.FieldUserValue.get_email() has been returning null for all users in Person or Group fields. This occures when I use getItems method. For example: var listName = "MyList"; var context = SP.ClientContext.get_current(); var web = context.get_web(); var list = web.get_lists().getByTitle(listName); var query= new SP.CamlQuery(); var items = list.getItems(query); context.load(items); context.executeQueryAsync(()=>{ var enumerator = items.getEnumerator(); while (enumerator.moveNext()) { var item = enumerator.get_current(); var fldValues = item.get_fieldValues(); console.log(fldValues["Editor"].get_email()) } }); I haven’t been able to find any information about changes related to this behavior. We’ve been using the Email property of user fields for years without any issues, and it has always worked as expected. It's documented here: https://learn.microsoft.com/ru-ru/dotnet/api/microsoft.sharepoint.client.fielduservalue.email?view=sharepoint-csom Does anyone know what might have changed or why this has stopped working?
