SharePoint Secrets

AZ-203: Developing Solutions for Microsoft Azure Passed.

AZ-400 Microsoft Azure DevOps Engineer Expert Passed.

An Agent that you set up and manage on you own to run jobs is a self-hosed agent.  You can use self-hosted agents in Azure Pipelines. In Azure DevOps Sever, agent pools are scoped to the entire server; so you can share the agent machines across projects and collections. When you create a pipeline, you specify which pool it uses. You create and manage agent pools from the agent pools tab in admin settings. Security of agent pools. Understanding how security works for agent pools helps you control sharing and use of agents. Roles are defined on each agent pool, and membership in these roles governs what operations you can perform on an agent pool. Role on an agent pool in organization settings Purpose Reader Members of this role can view the agent pool as well as agents. You typically use this to add operators that are responsible for monitoring the agents and their health. Service Account

How to easily deploy the Angular app to Azure by configuring build and release pipelines in Azure DevOps Create build pipeline definition To create a build pipeline that will create the optimized version of the app. Start with creating a new build pipeline from Pipelines >> Build on your team project in the browser. In this pipeline, you will add following tasks: Once this build pipeline is defined, you can queue the build. The created artifact should contain a file named dest.zip which will be used to do the deployment. Release & Deploy To do the deployment of the app, we will create a Release Pipeline. Under the Pipeline tab, select the build pipeline that you have created earlier as the artifact source to be deployed. Let the default version be the “Latest”. Under the Tasks tab, Select your Azure Account and authorize Azure DevOps to access resources from that Azure account when prompted. Now, select the task that is automatically ad

Detecting SharePoint environment from an SPFX. SPFX web parts can be added to modern and classic SharePoint pages and we might need to load different resources depending of the environment type. The environment type can be detected using the EnvironmentType enumeration, directly from your SPFX code. Member Description ClasicSharePoint Indicates that the framework was loaded from a classic SharePoint page Local Indicates that the framework was loaded from the workbench SharePoint Indicates that the framework was loaded by a client-rendered SharePoint page Test Represents the scenario of the framework hosted in a unit/integration test To detect the environment type start by importing the enumeration from the sp-core-library: import { Environment, EnvironmentType} from '@microsoft/sp-core-library'; Use the code below to target

The following REST commands are available for creating a modern SharePoint Communication site: Create . Create a new SharePoint site. Delete . Deletes a SharePoint site. Status . Get the status of a SharePoint site. The base URL for the REST commands is  _api/SPSiteManager . Create a modern site Using the following REST api you can create both Communication sites and non-group associated Team Sites. To specify which type of site to create you use the WebTemplate attribute. Use one of the following templates to select which type of site to create: Communication Site:  SITEPAGEPUBLISHING#0 non-group associated Team Site:  STS#3 JSON url: /_api/SPSiteManager/create accept: application/json;odata.metadata=none odata-version: 4.0 method: POST body: { "Title" : "Communication Site 1" , "Url" : "https://contoso.sharepoint.com/sites/commsite1" , "Lcid" : 1033 , "ShareByEmailEnabled" : false , &quo