Cortana voice assistant in Teams – Microsoft has planned to offer Cortana voice assistant in the Teams iOS and Android mobile app, which allows users to perform communication, collaboration, and meeting-related tasks by speaking the natural language. At the time of this release, the feature will be enabled only for users in the U.S. Expansion
The SharePoint classic popularity reports to be retired – as per Microsoft update MC195889 in November 2019, Microsoft had to retire Classic usage and popularity reports and these will no longer be available after August 7, 2020. Instead, users will be able to find site usage data through the modern Site Usage report. So, this is a
Retiring SharePoint 2010 Workflows: In a major development, Microsoft has announced the retirement of SharePoint 2010 workflows from the Microsoft 365 tenant. This move comes as part of Microsoft’s ongoing efforts to modernize and streamline its collaboration platform. SharePoint 2010 workflows have been widely used by organizations for their business processes, automation, and workflow management.
In this troubleshooting article, we will learn about How to fix “The term ‘Get-MsolUser’ is not recognized as the name of a cmdlet”. When we try to connect to Office 365 services, sometimes we may get the below error: “The term ‘Get-MsolUser’ is not recognized as the name of a cmdlet” How to fix the
Turn on inline message translation in Microsoft Teams – as per the “New Feature: Inline Chat message translation for iOS – [iOS] Teams Mobile On-Demand Chat Translation” June Microsoft 365 Roadmap update – the office 365 administrator can turn on inline message translation in Microsoft Teams from the Microsoft 365 admin center. So, in this
A couple of days back we have seen an error “Errors were found when compiling the workflow. The workflow files were saved but cannot be run” while trying to publish the SharePoint designer workflow. The error details were – “Unexpected error on server associating the workflow” This error we have noticed in the workflow of
In this “CRUD operations using SPFx no javascript framework” tutorial, we will learn about how we can do the SharePoint crud operations using the SPFx no javascript framework. Key Highlights: CRUD operations using SPFx no javascript framework Create the SharePoint project scaffolding Verify the project scaffolding Customize the code for SharePoint CRUD operation using the
The page could not be created. Custom Scripting might be deactivated on the destination site – these days I have been working with the SharePoint modern communication site – and facing different types of issues. One of the issues – I have faced is “The page could not be created. Custom Scripting might be deactivated
![[Fixed] Error – activate the SharePoint Server Publishing Infrastructure feature in SharePoint Online site](https://i0.wp.com/global-sharepoint.com/wp-content/uploads/2020/06/Fixed-Error-–-activate-the-SharePoint-Server-Publishing-Infrastructure-feature-in-SharePoint-Online-site.jpg?fit=965%2C540&ssl=1 "[Fixed] hidden error: Activate SharePoint Server Publishing Infrastructure feature in SharePoint Online site (Microsoft 365) 17")
Activate SharePoint server publishing infrastructure feature – When I was trying to activate the “SharePoint Server Publishing Infrastructure” feature in the SharePoint online communication site, getting the error – “Sorry, something went wrong An unexpected error has occurred. Technical Details, Troubleshoot issues with Microsoft SharePoint Foundation.“ Activate SharePoint server publishing infrastructure feature error When we
Discover private vs public office 365 groups on SharePoint online site – when we create a SharePoint modern team site, we can see the “Private group” or “Public group” tag beneath the site name (example below). In this article, I will explain what these are “Private groups” or “Public groups” are in the modern SharePoint
| Contact Us: support@global-sharepoint.com | Support this site| Privacy Policy| Sitemap | Copyright © 2024 Global SharePoint. All rights reserved. |
