Skip to main content

[Post Event] Global Microsoft 365 Developer Bootcamp, Cluj-Napoca, 2019

On October 16th, 2019 we hosted Global Microsoft 365 Developer Bootcamp in Cluj-Napoca. The event was organised by ITCa
mp Community with support from Microsoft and The Guild Hall. In comparison with other events in the past, this event was different from the topics that were discussed. The main focus was around Office 365 tools. We were surprised to find people that were not only very interesting about this topic but also are working in teams that manage and develop internal applications for Office 365.
What is Global Microsoft 365 Developer Bootcamp? Bootcamps are a free, one-day, hands-on training event led by Microsoft MVPs and community leaders with support from Microsoft. Developers worldwide are invited to attend a bootcamp to learn the latest on Microsoft 365 platform including Microsoft Graph, SharePoint Framework, Microsoft Teams, Office Add-ins and Actionable Messages, etc. and apply what you learn to your future projects.
The topics that were covered during the workshop were related to Graph API and Microsoft Flows.The topic that was covered by my were related to Microsoft Flows. You can find below the slides from my session.
See you next time!

Title: Empower your business with automate processes + tasks using Microsoft Flows
Abstract: Empower your business with automate processes + tasks using Microsoft Flows (Radu Vunvulea) – Join this session if you want to discover a tool that can be used to optimise your internal processes with just a few clicks. Microsoft Flows well integrated with Office 365 ecosystem, allowing us to remove the manual processes where human error can appear. We take a look at how we can automate the holiday approval requests end-two-end without writing a line of code (or this is what we hope 😊).
Slides:

Comments

Popular posts from this blog

Windows Docker Containers can make WIN32 API calls, use COM and ASP.NET WebForms

After the last post , I received two interesting questions related to Docker and Windows. People were interested if we do Win32 API calls from a Docker container and if there is support for COM. WIN32 Support To test calls to WIN32 API, let’s try to populate SYSTEM_INFO class. [StructLayout(LayoutKind.Sequential)] public struct SYSTEM_INFO { public uint dwOemId; public uint dwPageSize; public uint lpMinimumApplicationAddress; public uint lpMaximumApplicationAddress; public uint dwActiveProcessorMask; public uint dwNumberOfProcessors; public uint dwProcessorType; public uint dwAllocationGranularity; public uint dwProcessorLevel; public uint dwProcessorRevision; } ... [DllImport("kernel32")] static extern void GetSystemInfo(ref SYSTEM_INFO pSI); ... SYSTEM_INFO pSI = new SYSTEM_INFO(

Azure AD and AWS Cognito side-by-side

In the last few weeks, I was involved in multiple opportunities on Microsoft Azure and Amazon, where we had to analyse AWS Cognito, Azure AD and other solutions that are available on the market. I decided to consolidate in one post all features and differences that I identified for both of them that we should need to take into account. Take into account that Azure AD is an identity and access management services well integrated with Microsoft stack. In comparison, AWS Cognito is just a user sign-up, sign-in and access control and nothing more. The focus is not on the main features, is more on small things that can make a difference when you want to decide where we want to store and manage our users.  This information might be useful in the future when we need to decide where we want to keep and manage our users.  Feature Azure AD (B2C, B2C) AWS Cognito Access token lifetime Default 1h – the value is configurable 1h – cannot be modified

What to do when you hit the throughput limits of Azure Storage (Blobs)

In this post we will talk about how we can detect when we hit a throughput limit of Azure Storage and what we can do in that moment. Context If we take a look on Scalability Targets of Azure Storage ( https://azure.microsoft.com/en-us/documentation/articles/storage-scalability-targets/ ) we will observe that the limits are prety high. But, based on our business logic we can end up at this limits. If you create a system that is hitted by a high number of device, you can hit easily the total number of requests rate that can be done on a Storage Account. This limits on Azure is 20.000 IOPS (entities or messages per second) where (and this is very important) the size of the request is 1KB. Normally, if you make a load tests where 20.000 clients will hit different blobs storages from the same Azure Storage Account, this limits can be reached. How we can detect this problem? From client, we can detect that this limits was reached based on the HTTP error code that is returned by HTTP