Power Apps: source code edit for Canvas Apps in Visual Studio Code

by Contributed | Jul 1, 2021 | Technology

This article is contributed. See the original author and article here.

Why?

In April, I showed how to unpack and repack Power Apps .msapp files of Canvas Apps in the blog post Power Apps Source Code file editing for Canvas Apps (microsoft.com) Using this functionality, we can view and edit the source code of Canvas Apps. In a recent announcement (Canvas source code tool integrated with Power Platform CLI | Microsoft Power Apps), Microsoft announced that the same functionalities are now available within the Power Platform VS Code Extension of Visual Studio Code!

This means that after installing this extension, we can do the same unpacking and packing without leaving Visual Studio Code.

What?

This posts will show how easy it is to use Visual Studio Code so we can unpack and (re)pack .msapp files of Canvas Apps:

How?

1) First install the Power Platform VS Code Extension in your Visual Studio Code Client using the Visual Studio Marketplace (Power Platform VS Code Extension – Visual Studio Marketplace).

2) After installing the extension a computer restart may be required. We can from this moment on, run commands from within Visual Studio using the built-in Terminal.
In my example I saved the text file with commands as a Power Shell file (.ps1). In this type of files, short cuts like F8 can be used to run selected commands:

Notice the improved commands where referencing (input and output) files is much easier now!

In the Marketplace screenshot above, you can see that the extension is in Preview at the moment.
Please be aware of this and read the announcement link above on how to report issues.

Originally published at Power Apps: source code edit for Canvas Apps in Visual Studio Code » Knowhere365

SharePoint Online Multiple Files (Folder) Copy with Http Connector

by Contributed | Jul 1, 2021 | Technology

This article is contributed. See the original author and article here.

ADF does not directly support copying a folder/multiple files from SharePoint Online, but there are workarounds to achieve this. Two additional steps needed here as compared to single file copy are:

1. Get the list of files:




• User can maintain the file names in a text file manually, OR


• Use Web Activity to call SharePoint Rest API to get the list of files.




2. ForEach Activity to loop the list of relative file names and pass the file name to Copy Activity (Base URL changes a bit as compared to single file copy)

Below is how the pipeline flow would look like:

Web1 – Get the access token from SPO

Web2 – Get the list of files from SPO folder

ForEach1 – Loop the list of file names

Copy1 – Copy data with HTTP connector as source

Step1:

Grab Access token from SPO

Copy file from SharePoint Online leverages AAD/service principal authentication and SharePoint API to retrieve files.

1. Register SharePoint Application and Grant permission – https://docs.microsoft.com/en-us/azure/storage/common/storage-auth-aad-app?tabs=dotnet#register-your-application-with-an-azure-ad-tenant

         a) Register AAD Application

1. On Azure Portal, go to AAD app registration page: https://portal.azure.com/#blade/Microsoft_AAD_IAM/ActiveDirectoryMenuBlade/RegisteredApps 


2. New Registration à Enter your App name


3. Go to “Certificates & secrets”, create new client secret, you can set the expire to 1Y/2Y/Never

       b) Grant SharePoint site permission to your registered App (need site owner permission on SharePoint)

Full details on how to register app and also granting permissions is mentioned in prerequisites here – https://docs.microsoft.com/en-us/azure/data-factory/connector-sharepoint-online-list#prerequisites

     c) Create an ADF Pipeline. Start with creating a Web Activity to get the access token

• URL: https://accounts.accesscontrol.windows.net/[Tenant-ID]/tokens/OAuth/2 


• Method: POST

Headers:

• Content-Type: application/x-www-form-urlencoded


• Body: grant_type=client_credentials&client_id=[Client-ID]@[Tenant-ID]&client_secret=[Client-Secret]&resource=00000003-0000-0ff1-ce00-000000000000/[Tenant-Name].sharepoint.com@[Tenant-ID] 

Debug run to check if the activity succeeds and also check the activity output to see if it returns the access token in the payload. You can also verify the same using Postman client to check if the token is valid.

Step 2:

Get the list of Files

1. Create another Web Activity to get the list of files

• URL: https://{site_url}/_api/web/GetFolderByServerRelativeUrl(‘/Folder Name’)/Files


• Method: GET

Headers:

• Authorization: @{concat(‘Bearer ‘, activity(‘WebActivity1Name’).output.access_token)}


• Accept: application/json

 Debug run to see if the activity succeeds, and check it shows the list of files under the folder in the output.

Step 3:

Loop the list of relative file names

1. Create a ForEach Activity with inner Copy activity

• Items: @activity(‘WebActivity2Name’).output.value

Step 4:

Create Copy activity

1. New dataset -> HTTP -> Binary type:

    a) HTTP linked service

• Base URL:  https://<SiteUrl>/_api/web/GetFileByServerRelativeUrl (‘@{linkedService().FileName}’)/$value


• Authentication Type: Anonymous (use token configured on copy activity source)

    b) Configure copy activity HTTP source

         Dataset properties:

• Name: RelativeURL (Any name)


• Value: @{item().ServerRelativeUrl}


• Request method: GET


• Additional header: “Authorization: Bearer <accessToken>” (accessToken is generated in Step1)

Tip: You can test with a static access token gotten from the previous Web activity output first. You can also use expression (add dynamic content): @{concat(‘Authorization: Bearer ‘,activity(‘WebActivityName’).output.access_token)}

     c) Configure Linked Service properties

• Name: FileName (Any Name)


• Value: @dataset().RelativeURL

2. Create Copy sink as below

 Successful pipeline run as follows:              

Thanks to @Jijo Puthooran for helping me in authoring this blog.

What's new: ASIM Authentication, Process, Registry and enhanced Network schemas

by Contributed | Jul 1, 2021 | Technology

This article is contributed. See the original author and article here.

Hello everyone,   Continuing our normalization journey, we added to the networking and DNS schemas the Authentication, Process Events, and Registry Events schemas and delivered normalized content based on the two. We also added ARM template deployment and support for Microsoft Defender for Endpoints to the Network Schema.   Special thanks to @Yuval Naor , @Yaron Fruchtmann , and @Batami Gold , who made all this possible.   Why should you care?   Cross source detection: Normalized Authentication analytic rules work across sources, on-prem and cloud, now detecting attacks such as brute force or impossible travel across systems including Okta, AWS, and Azure. Source agnostic rules: process event analytics support any source that a customer may use to bring in the data, including Defender for Endpoint, Windows Events, and Sysmon. We are ready to add Sysmon for Linux and WEF once released! EDR support: Process, Registry, Network, and Authentication consist the core of EDR event telemetry. Ease of use: The Network Schema introduced last year is now easier to use with a single-click ARM template deployment.   Deploy the Authentication, Process Events, Registry Events, or Network Session parser packs in a single click using ARM templates.    Join us to learn more about the Azure Sentinel information model in two webinars: The Information Model: Understanding Normalization in Azure Sentinel Deep Dive into Azure Sentinel Normalizing Parsers and Normalized Content Why normalization, and what is the Azure Sentinel Information Model?   Working with various data types and tables together presents a challenge. You must become familiar with many different data types and schemas, write and use a unique set of analytics rules, workbooks, and hunting queries for each, even for those that share commonalities (for example, DNS servers). Correlation between the different data types necessary for investigation and hunting is also tricky.   The Azure Sentinel Information Model (ASIM) provides a seamless experience for handling various sources in uniform, normalized views. ASIM aligns with the Open-Source Security Events Metadata (OSSEM) common information model, promoting vendor agnostic, industry-wide normalization. ASIM: Allows source agnostic content and solutions Simplifies analyst use of the data in sentinel workspaces   The current implementation is based on query time normalization using KQL functions. And includes the following: Normalized schemas cover standard sets of predictable event types that are easy to work with and build unified capabilities. The schema defines which fields should represent an event, a normalized column naming convention, and a standard format for the field values. Parsers map existing data to the normalized schemas. Parsers are implemented using KQL functions. Content for each normalized schema includes analytics rules, workbooks, hunting queries, and additional content. This content works on any normalized data without the need to create source-specific content.

Ofer Shezaf Principal Product Manager, Azure Sentinel

CLI for Microsoft 365 v3.11

by Contributed | Jul 1, 2021 | Technology

This article is contributed. See the original author and article here.

CLI for Microsoft 365 v3.11

Manage Microsoft 365 and SharePoint Framework projects on any platform

m365 pa app get --displayName App

m365 spo site set --url https://contoso.sharepoint.com/sites/ModernSite --description "something"

m365 spo site classic set --url https://contoso.sharepoint.com/sites/ClassicSite --description "something"

m365 spfx doctor

m365 aad app role delete --appName "My app" --claim "Product.Get"

m365 aad app set --name "My app" --uri https://contoso.com/e75be2e1-0204-4f95-857d-51a37cf40be8

m365 aad o365group recyclebinitem clear

m365 cli config reset --key showHelpOnFailure

m365 cli config reset

m365 tenant report office365activationcounts

m365 tenant report office365activationsusercounts

m365 tenant report office365activationsuserdetail

m365 spfx package generate –webPartTitle “Amsterdam weather” –webPartDescription “Shows weather in Amsterdam” –packageName amsterdam-weather –html @amsterdam-weather.html –allowTenantWideDeployment –enableForTeams all

npm i -g @pnp/cli-microsoft365

docker run --rm -it m365pnp/cli-microsoft365:latest