New List Version History broken
Microsoft has updated how version history is displayed for SharePoint Lists. In my tenant the changes are not showing for changes made by a power automate flow. SharePoint did create a version but no changes are showing. There must have been changes or else a new version would not have been created.
PowerPoint Brand Images: folders appear as tabs, but images only show under “All”
Hi, I’m testing PowerPoint Brand Images with a SharePoint Organizational Asset Library and I’m seeing unexpected behaviour with folders. The image library is registered correctly as an ImageDocumentLibrary. PowerPoint detects the library and all images are visible under All. I created several first-level folders in SharePoint, for example: Photos Icons Logos Test PowerPoint correctly reads these folders and shows them as separate tabs in Insert > Pictures > Brand Images. The issue: the tabs remain empty. For example, I created a completely new folder called Test directly in SharePoint and uploaded a new PNG directly into that folder. Result: Test appears as a tab in PowerPoint the PNG appears under All the PNG does not appear under Test I see exactly the same behaviour in PowerPoint Desktop and PowerPoint for the web. I have already checked: OrgAssetType: ImageDocumentLibrary Private CDN: enabled library registered as Private CDN origin CopilotSearchable: enabled SharePoint Online Management Shell: 16.0.27515.12000 PowerPoint Microsoft 365 Beta Channel, version 2609, build 16.0.20416.20004, 64-bit direct upload through SharePoint instead of OneDrive/File Explorer completely new folder and image manual reindexing of the SharePoint library So PowerPoint finds both the folder names and the images, but the folder-to-image relationship does not seem to work in Brand Images. Has anyone successfully used first-level SharePoint folders as working tabs in the new PowerPoint Brand Images experience? Is there an additional configuration step required, or could this be an issue with folder-scoped retrieval in the current rollout?Strengthening Security in SharePoint Document Libraries: 5 Essential Best Practices
SharePoint Online has become a critical platform for storing, managing, and collaborating on documents across Microsoft 365 environments. Its flexibility and ease of access make it invaluable to modern organisations. However, if document libraries are not properly managed, businesses can face risks such as unauthorised access, accidental sharing of sensitive data, and compliance challenges. Effective SharePoint security is not about restricting productivity. It is about creating a secure framework that allows teams to collaborate confidently while ensuring business information remains protected. This article was written by https://www.bridgeall.com/a leading https://www.bridgeall.com/microsoft-365-consultancy/sharepoint/offering https://www.bridgeall.com/microsoft-365-consultancy/sharepoint/sharepoint-document-management-systems-implementation/ Five Ways to Improve SharePoint Document Library Security Limit Access Using Role-Based Permissions One of the most effective ways to secure SharePoint is by restricting access to only those who genuinely need it. Many organisations grant broad permissions across sites, creating unnecessary exposure. Following a least-access approach ensures users receive only the permissions required for their responsibilities. Rather than assigning permissions to individual files and folders, consider using Microsoft 365 Groups or SharePoint Security Groups to manage access centrally. This not only improves governance but also makes ongoing administration significantly easier. Review and Restrict External Sharing External collaboration is often necessary, but it can also become a source of data leakage if not controlled appropriately. Review sharing settings at both the tenant and site level to ensure they align with your organisation's security requirements. Good practices include: Preventing anonymous sharing links for libraries containing confidential information. Allowing access only to verified external users where appropriate. Applying expiry dates to shared links so access is automatically revoked after a defined period. Regularly auditing active external sharing relationships. By tightening these controls, organisations can reduce the likelihood of sensitive information being exposed outside the business. Protect Content with Sensitivity Labels Protecting the library itself is important, but protecting the documents within it adds another layer of security. Microsoft Purview Sensitivity Labels enable organisations to categorise content according to its sensitivity and automatically apply protection measures. Depending on the classification, labels can: Encrypt files. Restrict downloading, printing, or copying. Display visual markings such as headers, footers, or watermarks. Maintain protection even when a document is shared or moved outside SharePoint. This approach helps ensure security travels with the information rather than relying solely on where it is stored. Strengthen User Authentication Document-level security should always be backed by strong identity protection measures. Multi-Factor Authentication (MFA) remains one of the most effective ways to prevent unauthorised access resulting from compromised credentials. Combining MFA with Microsoft Entra Conditional Access policies provides even stronger protection. For example, organisations can: Block access from unmanaged devices. Restrict downloads on non-compliant endpoints. Trigger additional verification requirements for sign-ins from unfamiliar locations. Apply risk-based access controls based on user behaviour. These safeguards help ensure only trusted users and devices can access critical information. Continuously Monitor and Review Access Security is not a one-off project. Permissions and risks evolve over time, making ongoing monitoring essential. Microsoft Purview auditing capabilities provide visibility into activities such as file sharing, downloads, edits, deletions, and permission changes. Regular access reviews help identify: Outdated permissions. Dormant guest accounts. Excessive access rights. Unnecessary group memberships. Routine governance reviews help maintain a secure SharePoint environment and reduce the risk of privilege creep. Building a Secure and Collaborative SharePoint Environment A well-secured SharePoint platform should balance protection with usability. Organisations that invest in strong governance, identity controls, information protection, and ongoing monitoring are better positioned to support collaboration without compromising sensitive business data. By implementing these best practices, businesses can significantly reduce security risks while ensuring employees continue to work efficiently within Microsoft 365. At Bridgeall we offer a range of https://www.bridgeall.com/microsoft-365-consultancy/sharepoint/sharepoint-document-management-systems-implementation/ that help you build and maintain a secure platform of SharePoint document librarires.New List Version History broken
Microsoft has updated how version history is displayed for SharePoint Lists. In my tenant the changes are not showing for changes made by a power automate flow. SharePoint did create a version but no changes are showing. There must have been changes or else a new version would not have been created.
Custom Formatter for Read-Only Fields conditional based on other columns
Hello! Does anyone know if it's possible with the fieldsettings, readonly formatting, to make it conditional based on a Person field? It's a multi people field if that makes a difference? I ideally want to make certain fields read only based on who is viewing it (without having to use a Power App customised form!). This is what I want (but I know the syntax is likely all wrong!) but not sure if it's possible to use an IF statement with boolean statements? { "sections": [ {} ], "fieldsettings": [ { "name": "Comments", "readonly": "=if([$People.email] == me, false, true)" } ] }Android Webview not rendering the headers of SharePoint page
Workspace one Web Browser which is a secure enterprise browser app is built on Android System WebView, we have an Android WebView in which I am trying to load a SharePoint page. However, certain elements of the page are not being rendered or displayed correctly in the WebView. The same SharePoint page renders correctly in a Chrome browser, where all the expected elements are visible. Please refer to the attached image for comparison and reference. In Chrome In Android System Webview based Web Browser (for example Workspace ONE Web) We mainly wanted to know why is this behaviour specific to Android System WebView based browser.
MS List Column Width Forced
Hi, I've had a number of MS lists and been able to enter grid view and amend the width of columns and the text doesn't overflow which I want to keep the overall list width smaller; but as of yesterday all my columns are forced to be as wide as the text, meaning the that 1 column can be multiple screens wide for multi-line columns and they can't be resized smaller Is this a bug? Any help appreciated.
SharePoint Online / PnP Modern Search - Mudança no ranking dos resultados
Olá pessoal, Estou enfrentando um comportamento estranho em um ambiente SharePoint Online utilizando PnP Modern Search. Recentemente realizamos: Reindexação de uma biblioteca de documentos; Criação de novos mapeamentos no Search Schema para propriedades gerenciadas (RefinableString); Ajustes em refinadores da Busca Avançada. Após essas alterações, os documentos continuam sendo encontrados pela busca, porém percebemos uma mudança significativa no ranqueamento (relevância) dos resultados. Exemplo Existe um documento chamado: Manual - Chave de Segurança.pdf Ao pesquisar: Manual - Chave de Segurança, a busca retorna dezenas de resultados, porém esse documento não aparece entre os primeiros colocados. Entretanto, ao pesquisar com aspas: "Manual - Chave de Segurança", o documento é retornado imediatamente nas primeiras posições. O mesmo comportamento foi observado com outros documentos. O que já validamos O documento está ativo e vigente; O documento está indexado; O PnP Search Results utiliza a fonte LocalSharePointResults; Não existe ordenação customizada configurada; A busca retorna o documento corretamente quando utilizamos o termo exato entre aspas; O problema parece estar relacionado apenas ao ranking/relevância dos resultados. Dúvidas Uma reindexação de biblioteca pode alterar temporariamente o ranking dos resultados do SharePoint Search? Existe algum período de estabilização da relevância após uma reindexação? É recomendado utilizar XRANK para aumentar o peso dos campos Title ou Filename em cenários como esse? Existe alguma forma de priorizar documentos cujo nome do arquivo possua correspondência exata com o termo pesquisado sem perder os benefícios da relevância padrão do SharePoint? Alguém já passou por comportamento semelhante após reindexação ou alterações no Search Schema? Obrigado!
