[Elio Struyf] We all have these daily tasks that can be automated. Like checking if the backup job of your site completed, or looking how many times a file has been accessed, etc. These kinds of tasks are great to be automated by an Azure Functions. In this session, you will get an overview of what Azure Functions can do for you. With some demos, we go step by step through the creation, debugging and deployment process of these functions.

4. No hamsters are involved in the
process of running your functions

5. #SPSOslo - @eliostruyf
What is Serverless?
• AKA: FaaS (Function as a Service)
• Abstraction of servers
• Event-driven / instant scale
• Pay-per-use
• Micro-services  a way to decouple your monolithic applications
• No permanent storage, or it has to live somewhere else

7. Azure Functions
• Running pieces of code / scripts in the cloud
• Use the language of your preference
• C#, Node.js (JavaScript), F#, Python, PHP, PowerShell, Java
• Runs on Azure App Services
Use cases
• Timer function
• Call from SPFx web part
• Call from site design / flow
• …

8. Azure Functions – Pricing plans
Consumption plan
• € 0,17 per one million requests
• Scales up automatically
• Useful for smaller workloads
• Max. timeout of 10 minutes
App Service Plan
• Depends on the chosen plan
• You’re in control of scaling
• Faster / higher workload
• No timeout
Turn on: always on!

9. Azure Functions vs Web Jobs
Similarities
• Both can be scheduled or use a trigger (queue/blob/etc.)
• Both support C#, JavaScript, PS
Differences
• Pricing
• Development flexibility
• Easier to call Azure Functions (HTTP Trigger)
• It has its own UI in Azure
• Restrictions: 10 minutes timeout

10. Security options
Simple function authentication
• A code passed to the function
• On function level or app/admin level
https://<app-name>.azurewebsites.net/api/<function>?code=<code>
Azure AD Authentication
• Use OAuth token to call the function
• Great use in combination with SPFx solutions: AadHttpClient

11. #SPSOslo - @eliostruyf
Demo:
Checking out the portal

12. Local development

13. Local development options
Any stack / editor / platform
• azure-functions-cli
• Node.js
Visual Studio
• True C# functions
• VS2017 plugin

14. Useful CLI commands
• func init  initialize a new project
• func new  create a new function
• func host start  start up the functions runtime
• func azure login
• func azure functionapp fetch-app-settings <function-name>
• func azure storage fetch-connection-string <storage-name>

15. Debugging your functions
• Run: func host start
• Press F5 in Visual Studio Code and execute your function

16. #SPSOslo - @eliostruyf
Demo:
Writing your first Azure Function

17. #SPSOslo - @eliostruyf
Dependencies

18. #SPSOslo - @eliostruyf
Importing dependencies
• Node.js  npm install
• Make sure you create a package.json file (npm init)
• Best to be placed on the root level
• C#
• Use NuGet like you are used using it

19. #SPSOslo - @eliostruyf
Working with environment
variables

20. #SPSOslo - @eliostruyf
Working with environment variables
• Node.js
• process.env.<setting-name>
• C#
• GetEnvironmentVariable("<setting-name>")

21. #SPSOslo - @eliostruyf
Bindings

22. #SPSOslo - @eliostruyf
Working with bindings
Blob storage
Cosmos DB
Storage queue
Service bus
HTTP
…
Input
Blob storage
Cosmos DB
Storage queue
SendGrid
Twilio
…
Output

23. Queues are great for…
Anything that should be picked up by a longer running task
• SharePoint site provisioning
• SharePoint web hooks
• File processing (e.g. image size optimization)
QueueTrigger function
• Auto-runs your code when a message gets added
• If fails, it tried by default 5 times

24. Queues are great for…
Item 1
Item 2
Item 3
Item 4
Item 5
Item 6
Queue triggeredHTTP Triggered

25. Working with bindings
Add you bindings to the function.json file
{
"disabled": false,
"bindings": [{
"authLevel": "function",
"type": "httpTrigger",
"direction": "in",
"name": "req"
},
{
"type": "queue",
"name": "spfxversions",
"direction": "out",
"queueName": "versions",
"connection": "AzureWebJobsStorage"
}]
}

26. #SPSOslo - @eliostruyf
Demo:
Creating settings and bindings

27. #SPSOslo - @eliostruyf
Deployment

28. Deployment options
• Publish from Visual Studio
• CLI: func azure functionapp publish <function-name>
• Use local GIT repository
• Continuous deployment via VSTS

29. Do not forget to configure
your settings

30. #SPSOslo - @eliostruyf
Cold start

31. Optimizing the cold start
• Precompile C# created functions
• Not use the *.csx files
• Use Visual Studio + Azure development workload
• Use Azure Functions Pack for Node.js
• https://github.com/Azure/azure-functions-pack
• Uses Webpack
• Add your dependencies at root level of the host!

32. #SPSOslo - @eliostruyf
Demo:
Deployment via local GIT repo

33. #SPSOslo - @eliostruyf
What’s next?

34. #SPSOslo - @eliostruyf
Durable functions
• Extension on top of Azure Functions and WebJobs
• Write stateful functions
• Waiting for human interaction

35. Azure Functions – on-premises
https://elst.es/2GXcdyU

36. Questions?

37. Office Servers & Services MVP
Azure / Office 365 / SharePoint
@eliostruyf
www.eliostruyf.com
info@estruyf.be
Elio Struyf
Developer & Architect

38. #SPSOslo - @eliostruyf