Forem: WilliamRamirez

Powershell script to call microsoft graph and send email using azure app registration

WilliamRamirez — Mon, 04 Dec 2023 01:31:09 +0000

PowerShell script to call Microsoft Graph and send email using Azure app registration.

You will need to follow these steps:

-Register a new application in Azure and create a client secret for it. You will also need to assign the Mail.Send permission to the application in the API permissions section. You can refer to this article or this article for detailed instructions on how to do this.

-Connect to the Graph API using the client ID, client secret, and tenant ID of your application. You will need to get an access token and use it in the Authorization header of your requests. You can use the Invoke-RestMethod cmdlet to make HTTP requests to the Graph API. You can see an example of how to do this in this article.

-Send an email using the Graph API by specifying the sender, the subject, the body, and the recipients of the message. You can use the /users/{id}/sendMail endpoint to send an email on behalf of a user in your tenant. You will need to provide the message details in the JSON format in the body of your request. You can see an example of how to do this in this article.
Here is a sample PowerShell script that follows these steps and sends an email using the Graph API:

Replace these values with your own

$clientID = "yourClientID"
$clientSecret = "yourSecret"
$tenantID = "yourTenantID"
$mailSender = "sender@contoso.com"
$mailRecipient = "recipient@contoso.com"

Connect to Graph API

$tokenBody = @{
Grant_Type = "client_credentials"
Scope = "https://graph.microsoft.com/.default"
Client_Id = $clientID
Client_Secret = $clientSecret
}
$tokenResponse = Invoke-RestMethod -Uri "https://login.microsoftonline.com/$tenantID/oauth2/v2.0/token" -Method POST -Body $tokenBody
$headers = @{
"Authorization" = "Bearer $($tokenResponse.access_token)"
"Content-type" = "application/json"
}

Send email

$URLsend = "https://graph.microsoft.com/v1.0/users/$mailSender/sendMail"
$BodyJsonsend = @"
{
"message": {
"subject": "Hello from Graph API",
"body": {
"contentType": "HTML",
"content": "This email is sent via Microsoft Graph API"
},
"toRecipients": [
{
"emailAddress": {
"address": "$mailRecipient"
}
}
]
},
"saveToSentItems": "false"
}
"@
Invoke-RestMethod -Method POST -Uri $URLsend -Headers $headers -Body $BodyJsonsend`

Here is a sample PowerShell script that follows these steps and inserts an item to a SharePoint list using the Graph API:

# Replace these values with your own
$clientID = "yourClientID"
$clientSecret = "yourSecret"
$tenantID = "yourTenantID"
$siteID = "yourSiteID"
$listID = "yourListID"

# Connect to Graph API
$tokenBody = @{
    Grant_Type = "client_credentials"
    Scope = "https://graph.microsoft.com/.default"
    Client_Id = $clientID
    Client_Secret = $clientSecret
}
$tokenResponse = Invoke-RestMethod -Uri "https://login.microsoftonline.com/$tenantID/oauth2/v2.0/token" -Method POST -Body $tokenBody
$headers = @{
    "Authorization" = "Bearer $($tokenResponse.access_token)"
    "Content-type" = "application/json"
}

# Insert an item to a SharePoint list
$apiUrl = "https://graph.microsoft.com/v1.0/sites/$siteID/lists/$listID/items"
$itemBody = @{
    fields = @{
        Title = "Test Item"
        Color = "Red"
        Weight = 10
    }
}
$payload = ConvertTo-Json $itemBody -Depth 5
Invoke-RestMethod -Method POST -Uri $apiUrl -Headers $headers -Body $payload

PowerShell script that follows these steps and sends an email using the SharePoint SP.Utilities.Utility.SendEmail method:

# Replace these values with your own
$clientID = "yourClientID"
$clientSecret = "yourSecret"
$tenantID = "yourTenantID"
$siteID = "yourSiteID"
$mailSubject = "Hello from SharePoint"
$mailBody = "This email is sent via SharePoint SP.Utilities.Utility.SendEmail"
$mailTo = "recipient@contoso.com"
$mailFrom = "sender@contoso.com"

# Import the Microsoft.Graph module
Import-Module Microsoft.Graph

# Connect to Graph API using connect-mggraph
Connect-MgGraph -ClientSecretCredential $(New-Object Microsoft.Graph.Authentication.ClientSecretCredential -ArgumentList $tenantID, $clientID, $clientSecret)

# Get the request digest for the SharePoint site
$digestUrl = "https://graph.microsoft.com/v1.0/sites/$siteID/contextinfo"
$digestResponse = Invoke-MgGraphRequest -Method POST -Uri $digestUrl
$requestDigest = $digestResponse.FormDigestValue

# Send email using SharePoint SP.Utilities.Utility.SendEmail
$emailUrl = "https://graph.microsoft.com/v1.0/sites/$siteID/SP.Utilities.Utility.SendEmail"
$emailBody = @{
    properties = @{
        To = @($mailTo)
        Subject = $mailSubject
        Body = $mailBody
        From = $mailFrom
    }
}
$payload = ConvertTo-Json $emailBody -Depth 5
$headers = @{
    "X-RequestDigest" = $requestDigest
}
Invoke-MgGraphRequest -Method POST -Uri $emailUrl -Headers $headers -Body $payload

Starting Ukelele challenge

WilliamRamirez — Wed, 28 Jun 2023 11:32:17 +0000

Hello, everyone! I have some exciting news to share with you today. No, everything is about programming and working. I don't have any problems or worries at all, wait... I have big problems and some stress that I need to relax. In fact, I'm feeling so happy and grateful that I decided to take up a new hobby: learning the ukelele! I don't play any instrument, just my computer keyboard Lol.

You might be wondering why I chose the ukelele out of all the musical instruments out there. Well, let me tell you, it's such a fun and easy instrument to play and I have kids so I will learn with them. It only has four strings, so you don't have to worry about complicated fingerings or chords. It's also very portable and lightweight, so you can take it anywhere you go. And best of all, it sounds so cheerful and uplifting, just like how I feel right now.

I've always wanted to learn how to play a musical instrument, but I never had the time or the motivation before. But now that everything is working so well for me, I feel like I can do anything I set my mind to. I'm ready to challenge myself and learn something new. I've already ordered a ukelele online and I can't wait for it to arrive. I've also found some online tutorials and songs that I want to try out.

I'm so excited to start this new journey and share it with you all. I hope you'll join me in this adventure and maybe even pick up a ukelele yourself. Trust me, it's a lot of fun and it will make you feel happy too. No matter what's going on in your life, playing the ukelele will always brighten up your day. I will order my Ukelele, and I will share my progress in the next coming weeks. I will probably do the 30-day ukelele Challenge, see link below.

Thank you for reading this blog post and stay tuned for more updates on my ukelele progress. Until next time, keep smiling and keep strumming!

Ukulele Tutorials and Play-Alongs

Dylan Laine Music

Ukelele tips

30 day Ukelele Challenge

Environments in Power Apps. Setup your development environment and manage access

WilliamRamirez — Wed, 31 May 2023 23:54:55 +0000

Environments are a feature of Power Apps that allow you to store, manage, and share your business data, apps, and flows. Environments can help you separate your apps based on their roles, security requirements, or target audiences. For example, you can create different environments for testing and production, or for different teams or regions in your organization.

There are five types of environments in Power Apps: default, developer, production, sandbox, and trial. The default environment is automatically created for each tenant and is shared by all users. The developer environment is for individual use and has limited capacity and functionality. The production environment is for deploying and running your apps for end users. The sandbox environment is for testing and development purposes and can be reset at any time. The trial environment is for exploring the features of Power Apps for a limited time.

To create an environment, you need a license that allows environment creation and enough database storage capacity in your tenant. You also need to have the Environment Admin or Environment Maker role in the Power Platform admin center. You can create an environment with or without a database, depending on your needs and license type. You can also move resources between environments or delete environments that you no longer need.

Reasons to use environments

Reasons to create environments beyond the default one include:

Separate app development by department - In a large organization, each department can work in a different environment. That way, department employees see only apps and company data that are appropriate to their needs.

Support application lifecycle management (ALM) - Separate environments let you separate apps that are in development stages from ones that have already been shared. Alternatively, you might want to use a trial environment so that you can receive feedback from employees before publishing the final app. For some organizations, showing apps before they're completely developed and published can present security concerns.

Manage data access - Each environment can have its own source of business data, called a database for Microsoft Dataverse. Other data connections are specific to an environment and can't be shared across environments.

Per Microsoft Documentation

Create an environment

Only an admin can create environments. If you aren't an admin, this information can still be helpful when you talk to your admin about setting up environments.

On the make.powerapps.com home page, select the gear icon near the upper-right corner and then select Admin center.

You can also go directly to https://admin.powerplatform.microsoft.com

In Microsoft Power Platform admin center, select + New.
In the New environment dialog box, enter a name for the environment and then select a region and an environment type.
To the left of Create a database for this environment, select the toggle to Yes.
Select Next.
Select the currency and language for the data that is stored in the database. You can't change the currency or language after the database is created.
Select Save.

It might take several minutes to create the database on Dataverse. After the database is created, the new environment appears in the list of environments on the Environments page.

You now have a new environment to work in. If you go back to make.powerapps.com, you'll see it in the environments list.

Manage access to an environment.

By default, you can access an environment in one of two ways:

System admin - A system admin has full permissions to create and manage environments.

Environment maker - An environment maker can view all apps in that environment, create apps, and work with Dataverse (other permissions apply).

Environment admins can create other security roles as needed. They can also add and assign users to these roles.

Start by going to https://admin.powerplatform.microsoft.com
On the left pane, Environments should be selected by default, if it isn't, select Environments.
Select the test environment that you created, and then select Settings at the top.
Select the Users + permissions dropdown and select Users.
Select Add user at the top and add the user by entering the email address of the user in your organization and then selecting Add. Wait a few minutes for the user to be added.
To manage the roles and information of a user, select the user’s Name. A new tab opens with the Dynamics 365 view of that user.
Select Manage Roles on the top bar.
In the Manage User Roles box, select the role(s) for the user. In this example, assign the user to the Environment Maker role.
Select OK.
The changes are then saved, so you can close the Dynamics 365 tab in your browser when done.

Congratulations. I can say that set up environments so that you can separate a working environment from the one that you want to share with your team will help you to learn, test, and create a minimum viable product. In conclusion, environments can be shared with specific users, allowing you to manage who can access certain data.

Control Node.js versions with Node Version Manager (NVM) to develop SPFx solutions for different SharePoint environments

WilliamRamirez — Mon, 29 May 2023 00:36:30 +0000

NVM for Windows

The Microsoft/npm/Google recommended Node.js version manager for Windows.

NVM (Node Version Manager) is a tool that allows you to install and switch between different versions of Node.js on your machine. This can be useful for developing SPFx (SharePoint Framework) solutions that require specific Node.js versions. For example, SPFx v1.17.1 requires Node.js v16 LTS, while SPFx v1.4.1 for SharePoint Server 2019 requires Node.js v8 LTS .

To use NVM for SPFx development, you need to follow these steps :

Install NVM from https://github.com/coreybutler/nvm-windows/releases or use choco install nvm if you have Chocolatey installed.
Run nvm install <version> to install the desired Node.js versions, such as nvm install 16.13.0 and nvm install 8.17.0.
Run nvm use <version> to switch between Node.js versions, such as nvm use 16.13.0 or nvm use 8.17.0.
Install the SPFx development tools with npm install -g yo @microsoft/generator-sharepoint gulp.
Create a new SPFx project with yo @microsoft/sharepoint and follow the prompts.
Run gulp serve to start the local web server and test your SPFx solution.

Using NVM can help you avoid compatibility issues and errors when developing SPFx solutions for different SharePoint environments.

I did an example after running nvm install 16.18.0 and nvm use 16.18.0:

1) I ran in the Powershell cli:

npm install gulp-cli yo @microsoft/generator-sharepoint --global

2) Created boiler plate web part code

yo @microsoft/sharepoint

3) Updated SharePoint URL

Locate and open the file ./config/serve.json in your project.

{
  "$schema": "https://developer.microsoft.com/json-schemas/core-build/serve.schema.json",
  "port": 4321,
  "https": true,
  "initialPage": "https://enter-your-SharePoint-site/_layouts/workbench.aspx"
}

4) Trust local environment.

gulp trust-dev-cert
gulp serve

or  you can use 

gulp serve --nobrowser

5) Here is the result

Keep learning, testing, and deploying. Then, repeat. Have fun!

Source:
Setup dev environment

Webpart hello world

Sharepoint dev examples to try

WilliamRamirez — Thu, 06 Apr 2023 03:38:29 +0000

Consume the Microsoft Graph in the SharePoint Framework

Consume enterprise APIs secured with Azure AD in SharePoint Framework

Use app-only authentication with the Microsoft Graph PowerShell SDK

M365 Sites to follow

WilliamRamirez — Thu, 06 Apr 2023 03:25:10 +0000

Lazy Admin
Microsoft Loop – What you need to know and How to use it

Complete Guide to Enable Microsoft Loop App

MAUI, Security, Sharepoint

WilliamRamirez — Thu, 06 Apr 2023 03:18:21 +0000

Security

OpenID Connect authentication with Azure Active Directory

Enable your ASP.NET Core web app to sign in users and call Microsoft Graph with the Microsoft identity platform

Tutorial - Enable your Web Apps to sign-in users and call APIs with the Microsoft identity platform for developers

Claims xray in azure AD with directory extension

Registering the sample apps with the Microsoft identity platform and updating the configuration files using PowerShell

Configure identity providers

Overview MSAL

Build .NET apps with Microsoft Graph

Enable your ASP.NET Core web app to sign in users and call Microsoft Graph with the Microsoft identity platform

Sharepoint
Granting access via Azure AD App-Only
Modernization scanner

Sharepoint Online not modern and Postman

SharePoint Online REST API access using AAD Client ID and Client Secret

Get metadata for a list

MAUI
MAUI Github repo
What's new in MAUI-Expander
MAUI communication Microsoft.Maui.Networking
MAUI Samples V.7
MAUI Samples v.7
https://www.youtube.com/watch?v=NPJhrftkqeg

Utils
Scoop Util

Fun
Cub with staples

.NET MAUI

WilliamRamirez — Wed, 28 Sep 2022 23:01:42 +0000

Tutorial: Create a web API with ASP.NET Core

Announcing the .NET MAUI Beautiful UI Challenge

Snppts is a community-run website helping aggregate beautiful .NET MAUI UI snippets for and from the community.

.NET Architecture Guides

Tutorial: Create a .NET MAUI app using the Microsoft Graph SDK

Use Postman with the Microsoft Graph API

Tutorial: Create a .NET class library using Visual Studio for Mac

.NET MAUI eBook Now Available – Enterprise Application Patterns

.NET Multi-platform App UI documentation

Tutorial - Enable your Web Apps to sign-in users and call APIs with the Microsoft identity platform for developers

Installing dotnet try in MacOS and try .NET Offline

WilliamRamirez — Wed, 04 Nov 2020 18:17:41 +0000

I read that Try .NET is an interactive documentation generator for .NET Core. Best of all is open source.

I wanted to be able to run dotnet try samples in macOS that I found in Github and same time being able to build a tutorial.

Installed dotnet

Downloaded the current .Net Core and installed
https://dotnet.microsoft.com/download/dotnet/curren

Installed the dotnet try tool using the terminal

dotnet tool install --global Microsoft.dotnet-try --version 1.0.20474.1

Cloned the repository

git clone https://github.com/dotnet/try-samples

I just set the current directory to one of the sample tutorials and ran code below

dotnet try

This launched the browser.

For more dotnet CLI commands I would recommend to visit Microsoft docs