The need for Digitization is constantly growing and there are never enough resources (Cost-Scope-Schedule) to fulfil all the requirements, therefore Microsoft on 25th May during the recent Microsoft Build event, has introduced the “Express Design – Build an app in seconds” which is a new Power Apps features that accelerate the process for getting started by taking existing content (e.g.: a picture of your paper form, a screenshot of a design, a PPT, a PDF or a Figma design file) and converting them in working Power App with UI and data without requiring the maker to learn how to build an app.
This magic is done using Azure Cognitive Vision OCR model to recognize the text from your image as well as the Azure Computer Vision Object Detection model to recognize the controls on the image whether it’s a text input, a label or radio button, etc.
After that, even though it’s optional, however, it’s recommended for you to set up the data through dataverse, so you will have your data stored in dataverse.
We have got three different options and we are going to see each one of them
Image to app
Figma to app
API to app
Image to app
Image to app
Let’s get started by building an Image to app
1. On Power Apps, click Create and select Image (preview)
Image (preview)
2. The Upload an image screen appears, where either you upload an image of your own or start with some sample images – in our case, let us upload the following Car Details Application Wireframe
Upload an imageCar Details Wireframe
3. After Azure identifies the component, tag and assign each component as per the requirements
Assign components
4. Next the system allows you to create a new table in Dataverse (recommended), or simply skip it for now.
5. In this step, map the column as per the required data type, review then create.
Columns mapping
And voila, in a few minutes – Power Apps has provisioned the app as per the given input!!!
Car details application
This is a whole new world of possibilities for the citizen developers, those architects or building technicians who are looking for a genuine alternative to building an app – truly it is Empowering every person and every business on the planet to achieve more.
There was a requirement that any user in the organization can update his/her profile picture across all Office 365 apps – the approach was quite straight forward: use Power Apps, save the user data in SharePoint and use Power Automate HTTP connector to do a POST using a Graph API endpoint – however, it seems now that the Power Automate HTTP is a Premium connector which becomes overpriced as all the users in the organization are going to use it, therefore used Azure Web Jobs which did the job well. Note that WebJobs provide an easy way to run scripts or programs as background processes in the context of your app.
– Under Project Details, select Subscription and Resource Group.
– Under Instance Details, provide a descriptive Name, and set as follows – Publish: Code, Runtime stack: latest .Net version, Operating System: Window.
B2. Download the publish profile
Once the Web App is provisionned, Get the publish profile from the Overview menu.
B3. Create a Console Application using Visual Studio 2017 or later.
Once created, right-click on the Project and click Publish as Azure WebJob… to create the Web Job within Visual Studio.
– Provide a descriptive WebJob name.
– Select a WebJob run mode: Run Continuously or Run on Demand. (There is a Scheduled run option as well which we will see in the section B5).
B4. On the next Publish screen, Import the profile settings which you saved in steps B2.
B5. Change the Webjob run mode to Scheduled.
Open the webjob-publish-settings.json within Properties and change the code as follows:
There was a requirement that any user in the organization can update his/her profile picture across all Office 365 apps – the approach was quite straight forward: use Power Apps, save the user data in SharePoint and use Power Automate HTTP connector to do a POST using a Graph API endpoint – however, it seems now that the Power Automate HTTP is a Premium connector which becomes overpriced as all the users in the organization are going to use it, therefore used Azure Web Jobs which did the job well. Note that WebJobs provide an easy way to run scripts or programs as background processes in the context of your app.
Let’s get started.
A. Power Apps & SharePoint
A1. Create a new blank app with a Tablet layout preferably.
A2. Insert an Add picture control to upload the image.
Set the OnSelect property as follows
Set(CapturedPic, UploadedImage1.Image); Set(vImg,JSON(UploadedImage1.Image,JSONFormat.IncludeBinaryData)); If(Value(Text(Len(vImg) * .00000073,”[$-en-US]##.##”)) >= 4, Notify(“Please choose an image less than 4 Mb”),””);
A3. Insert an Image control to validate the uploaded image.
In the Image property, set it as CapturedPic
A4. Add some labels to make the app more descriptive as follows:
It is preferable to show the image size in a label, the reason being is that Graph API support only an image size less than 4Mb, to show the size set the Text as: “Image size: ” & Text(Len(vImg)*.00000073,”[$-en-US]##.##”) & ” Mb”
A5. Now comes the submission of data to SharePoint
On the OnSelect button, add the following code
//Used for delegation purpose
ClearCollect(
userImage,
imgCapture.Image
);
//Checking whether the entry of the same user exists in the list
ClearCollect(
IsEntryExists,
Filter(
UsersProfileData,
EmployeeUPN = CurrentUser.Email
)
);
//If so then Update otherwise Add
If(
CountRows(IsEntryExists) > 0,
Patch(
UsersProfileData,
LookUp(
UsersProfileData,
EmployeeUPN = CurrentUser.Email
),
{
Title: User().FullName,
EmployeeDisplayName: CurrentUser.FullName,
EmployeeUPN: CurrentUser.Email,
EmployeeMail: Office365Users.MyProfile().Mail,
EmployeePhotoApproval: If(
chkApprove.Value = true,
"yes",
"no"
),
IsUpdated: false,
UserLanguage:Lower(Language()),
EmployeePhotoAsBase64: First(userImage).Url,
EmployeePhotoAsText: Substitute(
JSON(
imgCapture.Image,
JSONFormat.IncludeBinaryData
),
"""",
""
)
}
),
Patch(
UsersProfileData,
Defaults(UsersProfileData),
{
Title: User().FullName,
EmployeeDisplayName: CurrentUser.FullName,
EmployeeUPN: CurrentUser.Email,
EmployeeMail: Office365Users.MyProfile().Mail,
EmployeePhotoApproval: If(
chkApprove.Value = true,
"yes",
"no"
),
IsUpdated: false,
IsDeleted: false,
UserLanguage:Lower(Language()),
EmployeePhotoAsBase64: First(userImage).Url,
EmployeePhotoAsText: Substitute(
JSON(
imgCapture.Image,
JSONFormat.IncludeBinaryData
),
"""",
""
)
}
)
);
//Reset all controls and notify
Set(
CapturedPic,
Blank()
);
Reset(chkApprove);
Reset(AddMediaButton1);
Notify("Photo submitted successfully - please check after sometimes in Delve portal.");
In the year 2010 when I took MOSS 2007 Training conducted by an MCT who is now my friend – I admired him for being in such a high position – Microsoft Certified Trainers (MCTs) are the premier technical and instructional experts in Microsoft technologies.
I never in my life dreamed that one day I will become a Microsoft Certified Trainer which has provided me with immense satisfaction and I intend to honour that trust from Microsoft.
As an active MCT now, I will get exclusive benefits as an MCT including access to the complete library of official Microsoft training and certification products, substantial discounts on exams, books, and Microsoft products.
In addition, MCTs will be able to use Microsoft readiness resources to help enhance their training career and engage with other MCT members in an online community forum. They will also receive invitations to exclusive Microsoft and local MCT community events.
This time we are going to see together how to restrict some specific users or set of users or groups in Azure AD tenant – this scenario is useful when you want to provide access to some specific department only in your organization e.g.: Finance Department.
It is important to note that Applications registered in an Azure Active Directory (Azure AD) tenant are, by default, available to all users of the tenant who authenticate successfully – therefore the following steps are necessary to update the application to require user assignment.
To update an application to require user assignment, you must be owner of the application under Enterprise apps, or be assigned one of Global administrator, Application administrator or Cloud application administrator directory roles.
If you have access to multiple tenants, use the Directory + subscription filter in the top menu to select the tenant in which you want to register an application.
Search for and select Azure Active Directory.
Under Manage, select Enterprise Applications > All applications.
Select the application you want to configure to require assignment. Use the filters at the top of the window to search for a specific application.
On the application’s Overview page, under Manage, select Properties.
Locate the setting User assignment required? and set it to Yes. When this option is set to Yes, users and services attempting to access the application or services must first be assigned for this application, or they won’t be able to sign-in or obtain an access token.
Select Save.
Assign the app to users and groups
Once you’ve configured your app to enable user assignment, you can go ahead and assign the app to users and groups.
Under Manage, select the Users and groups > Add user/group .
Select the Users selector. A list of users and security groups will be shown along with a textbox to search and locate a certain user or group. This screen allows you to select multiple users and groups in one go.
Once you are done selecting the users and groups, select Select.
(Optional) If you have defined app roles in your application, you can use the Select role option to assign the app role to the selected users and groups.
Select Assign to complete the assignments of the app to the users and groups.
Confirm that the users and groups you added are showing up in the updated Users and groups list.
and bang!!! only the set of users which you specified are now able to access the app now.
With all major deployment going to Azure WebApps – it is imperative for our organization to handle the Authentication from AAD perspective; so in order to use AAD Authentication, the approach is to use an App which serve as a “Bridge” between AAD & the solution which consume it. Follow this link If you wanna know more on how to Register an app with the Azure Active Directory v2.0 endpoint
The requirement is based on a scenario where the user use the browser to access an ASP.NET website which authenticate the user automatically.
These libraries enable single sign-on (SSO) by using OpenID Connect through cookie-based authentication. After authentication is completed and the token representing the user is sent to your application, OWIN middleware creates a session cookie. The browser then uses this cookie on subsequent requests so that the user doesn’t have to retype the password, and no additional verification is needed.
Configure the authentication pipeline
The following steps are used to create an OWIN middleware Startup class to configure OpenID Connect authentication. This class is executed automatically when your IIS process starts. (If your project doesn’t have a Startup.cs file in the root folder:)
1. Add OWIN and Microsoft.IdentityModel references to Startup.cs:
using Microsoft.Owin;
using Owin;
using Microsoft.IdentityModel.Protocols.OpenIdConnect;
using Microsoft.IdentityModel.Tokens;
using Microsoft.Owin.Security;
using Microsoft.Owin.Security.Cookies;
using Microsoft.Owin.Security.OpenIdConnect;
using Microsoft.Owin.Security.Notifications;
2. Replace Startup class with the following code:
public class Startup
{
// The Client ID is used by the application to uniquely identify itself to Microsoft identity platform.
string clientId = System.Configuration.ConfigurationManager.AppSettings["ClientId"];
// RedirectUri is the URL where the user will be redirected to after they sign in.
string redirectUri = System.Configuration.ConfigurationManager.AppSettings["RedirectUri"];
// Tenant is the tenant ID (e.g. contoso.onmicrosoft.com, or 'common' for multi-tenant)
static string tenant = System.Configuration.ConfigurationManager.AppSettings["Tenant"];
// Authority is the URL for authority, composed of the Microsoft identity platform and the tenant name (e.g. https://login.microsoftonline.com/contoso.onmicrosoft.com/v2.0)
string authority = String.Format(System.Globalization.CultureInfo.InvariantCulture, System.Configuration.ConfigurationManager.AppSettings["Authority"], tenant);
/// <summary>
/// Configure OWIN to use OpenIdConnect
/// </summary>
/// <param name="app"></param>
public void Configuration(IAppBuilder app)
{
app.SetDefaultSignInAsAuthenticationType(CookieAuthenticationDefaults.AuthenticationType);
//"Katana bug #197" - https://stackoverflow.com/questions/49944071/idx21323-openidconnectprotocolvalidationcontext-nonce-was-null-openidconnectpro
app.UseKentorOwinCookieSaver();
app.UseCookieAuthentication(new CookieAuthenticationOptions());
app.UseOpenIdConnectAuthentication(
new OpenIdConnectAuthenticationOptions
{
// Sets the ClientId, authority, RedirectUri as obtained from web.config
ClientId = clientId,
Authority = authority,
RedirectUri = redirectUri,
// PostLogoutRedirectUri is the page that users will be redirected to after sign-out. In this case, it is using the home page
PostLogoutRedirectUri = redirectUri,
Scope = OpenIdConnectScope.OpenIdProfile,
// ResponseType is set to request the code id_token - which contains basic information about the signed-in user
ResponseType = OpenIdConnectResponseType.CodeIdToken,
// ValidateIssuer set to false to allow personal and work accounts from any organization to sign in to your application
// To only allow users from a single organizations, set ValidateIssuer to true and 'tenant' setting in web.config to the tenant name
// To allow users from only a list of specific organizations, set ValidateIssuer to true and use ValidIssuers parameter
TokenValidationParameters = new TokenValidationParameters()
{
ValidateIssuer = false // This is a simplification
},
// OpenIdConnectAuthenticationNotifications configures OWIN to send notification of failed authentications to OnAuthenticationFailed method
Notifications = new OpenIdConnectAuthenticationNotifications
{
AuthenticationFailed = OnAuthenticationFailed
}
}
);
}
/// <summary>
/// Handle failed authentication requests by redirecting the user to the home page with an error in the query string
/// </summary>
/// <param name="context"></param>
/// <returns></returns>
private Task OnAuthenticationFailed(AuthenticationFailedNotification<OpenIdConnectMessage, OpenIdConnectAuthenticationOptions> context)
{
context.HandleResponse();
context.Response.Redirect("/?errormessage=" + context.Exception.Message);
return Task.FromResult(0);
}
}
3. Handle sign-in and sign-out requests:
In your Start Page where you want to handle authentication, add the following two methods to handle sign-in and sign-out to your controller by initiating an authentication challenge:
/// <summary>
/// Send an OpenID Connect sign-in request.
/// Alternatively, you can just decorate the SignIn method with the [Authorize] attribute
/// </summary>
public void SignIn()
{
if (!Request.IsAuthenticated)
{
HttpContext.GetOwinContext().Authentication.Challenge(
new AuthenticationProperties{ RedirectUri = "/" },
OpenIdConnectAuthenticationDefaults.AuthenticationType);
}
}
/// <summary>
/// Send an OpenID Connect sign-out request.
/// </summary>
public void SignOut()
{
HttpContext.GetOwinContext().Authentication.SignOut(
OpenIdConnectAuthenticationDefaults.AuthenticationType,
CookieAuthenticationDefaults.AuthenticationType);
}
protected void Page_Load(object sender, EventArgs e)
{
if (Request.IsAuthenticated)
{
Session["UserName"] = System.Security.Claims.ClaimsPrincipal.Current.FindFirst("name").Value;
Session["UserUPN"] = System.Security.Claims.ClaimsPrincipal.Current.FindFirst("preferred_username").Value;
Session["UserEmail"] = System.Security.Claims.ClaimsPrincipal.Current.FindFirst("http://schemas.xmlsoap.org/ws/2005/05/identity/claims/emailaddress").Value;
}
else
SignIn();
}
Et voila! It is very easy to set up and use and it works like a charm.
One of my recent task was to translate a word document into a pdf from a web application hosted in Azure Web App – therefore the code has to process at the Azure side.
Initially, I thought a traditional approach would work such as Interop or some free Api easily available on the net, however to my great surprise the code was throwing the following exception A generic error occurred in GDI+.
What I learned from this is that all Azure Web Apps (as well as Mobile App/Services, WebJobs, and Functions) run in a secure environment called a sandbox. Each app runs inside its own sandbox, isolating its execution from other instances on the same machine as well as providing an additional degree of security and privacy that would otherwise not be available. The sandbox mechanism aims to ensure that each app running on a machine will have a minimum guaranteed level of service; furthermore, the runtime limits enforced by the sandbox protect apps from being adversely affected by other resource-intensive apps which may be running on the same machine.
The sandbox generally aims to restrict access to shared components of Windows. Unfortunately, many core components of Windows have been designed as shared components: the registry, cryptography, and graphics subsystems, among others. For the sake of radical attack surface area reduction, the sandbox prevents almost all of the Win32k.sys APIs from being called, which practically means that most of User32/GDI32 system calls are blocked. For most applications, this is not an issue since most Azure Web Apps do not require access to Windows UI functionality (they are web applications after all). Since all the major libraries use a lot of GDI calls during the PDF conversion, the default rendering engine does not work on Azure Web Apps. You can find more information about those sandbox restrictions on https://github.com/projectkudu/kudu/wiki/Azure-Web-App-sandbox#win32ksys-user32gdi32-restrictions.
So now the solution is to find an approach to convert the PDF within Azure – luckily I came across a blog from Philipp Bauknecht which is leveraging Microsoft Graph to convert a document to PDF – let us see how.
There are several steps, which you have to perform in the correct order:
Step 1: Create an App registration in Azure AD and assign the required permissions
1.1 Go to https://portal.azure.com, then Azure Active Directory and select App Registrations; Click on New registration, provide a name then click on Register
1.2 Once the app is provisioned, on the left navigation blade click on Certificates & secrets; Click on New client secret to create one, then save the value of the secret for later use.
1.3 Go to API permissions, then click on Add a permission then Microsoft Graph, then choose Application permissions to add the following permissions (Admin consent is a must):
1.4 Go to Overview and save the values of Application (client) Id and Directory (tenant) Id for later use.
Step 2: Create a new Azure Functions app using Visual Studio 2019
Open Visual Studio 2019 and Create a new project in which choose Azure Functions
Step 3: Create an OAuth2 authentication service to request an access token to call the Microsoft Graph
This class is responsible to get the access token.
using Microsoft.Extensions.Options;
using Newtonsoft.Json;
using System.Collections.Generic;
using System.Net.Http;
using System.Threading.Tasks;
namespace PdfConversionFunctionApp
{
public class AuthenticationService
{
public static async Task<string> GetAccessTokenAsync(ApiConfig _apiConfig)
{
var values = new List<KeyValuePair<string, string>>
{
new KeyValuePair<string, string>("client_id", _apiConfig.ClientId),
new KeyValuePair<string, string>("client_secret", _apiConfig.ClientSecret),
new KeyValuePair<string, string>("scope", _apiConfig.Scope),
new KeyValuePair<string, string>("grant_type", _apiConfig.GrantType),
new KeyValuePair<string, string>("resource", _apiConfig.Resource)
};
var client = new HttpClient();
var requestUrl = $"{_apiConfig.Endpoint}{_apiConfig.TenantId}/oauth2/token";
var requestContent = new FormUrlEncodedContent(values);
var response = await client.PostAsync(requestUrl, requestContent);
var responseBody = await response.Content.ReadAsStringAsync();
dynamic tokenResponse = JsonConvert.DeserializeObject(responseBody);
return tokenResponse?.access_token;
}
}
}
Step 4: Create a File Service to upload, convert and delete files using the Microsoft Graph
This class is responsible to upload, convert and delete the file.
using Newtonsoft.Json;
using System;
using System.IO;
using System.Net.Http;
using System.Net.Http.Headers;
using System.Threading.Tasks;
namespace PdfConversionFunctionApp
{
public class FileService
{
private readonly ApiConfig _apiConfig;
private HttpClient _httpClient;
public FileService(ApiConfig apiConfig)
{
_apiConfig = apiConfig;
}
private async Task<HttpClient> CreateAuthorizedHttpClient()
{
if (_httpClient != null)
{
return _httpClient;
}
var token = await AuthenticationService.GetAccessTokenAsync(_apiConfig);
_httpClient = new HttpClient();
_httpClient.DefaultRequestHeaders.Add("Authorization", $"Bearer {token}");
return _httpClient;
}
public async Task<string> UploadStreamAsync(string path, Stream content, string contentType)
{
var httpClient = await CreateAuthorizedHttpClient();
string tmpFileName = $"{Guid.NewGuid().ToString()}{MimeTypes.MimeTypeMap.GetExtension(contentType)}";
string requestUrl = $"{path}root:/{tmpFileName}:/content";
var requestContent = new StreamContent(content);
requestContent.Headers.ContentType = new MediaTypeHeaderValue(contentType);
var response = await httpClient.PutAsync(requestUrl, requestContent);
if (response.IsSuccessStatusCode)
{
dynamic file = JsonConvert.DeserializeObject(await response.Content.ReadAsStringAsync());
return file?.id;
}
else
{
var message = await response.Content.ReadAsStringAsync();
throw new Exception($"Upload file failed with status {response.StatusCode} and message {message}");
}
}
public async Task<byte[]> DownloadConvertedFileAsync(string path, string fileId, string targetFormat)
{
var httpClient = await CreateAuthorizedHttpClient();
var requestUrl = $"{path}{fileId}/content?format={targetFormat}";
var response = await httpClient.GetAsync(requestUrl);
if (response.IsSuccessStatusCode)
{
var fileContent = await response.Content.ReadAsByteArrayAsync();
return fileContent;
}
else
{
var message = await response.Content.ReadAsStringAsync();
throw new Exception($"Download of converted file failed with status {response.StatusCode} and message {message}");
}
}
public async Task DeleteFileAsync(string path, string fileId)
{
var httpClient = await CreateAuthorizedHttpClient();
var requestUrl = $"{path}{fileId}";
var response = await httpClient.DeleteAsync(requestUrl);
if (!response.IsSuccessStatusCode)
{
var message = await response.Content.ReadAsStringAsync();
throw new Exception($"Delete file failed with status {response.StatusCode} and message {message}");
}
}
}
}
Step 5: Setup Dependency Injection
5.1 In order to use the FileService and the Configuration properties (local & in Azure), we need to set dependency injection. To use dependency injection in Azure Function app we need to add the package Microsoft.Azure.Functions.Extensions to our app using Nuget.
using Microsoft.Azure.Functions.Extensions.DependencyInjection;
using Microsoft.Extensions.Configuration;
using Microsoft.Extensions.DependencyInjection;
using System;
using System.IO;
using System.Reflection;
[assembly: FunctionsStartup(typeof(PdfConversionFunctionApp.Startup))]
namespace PdfConversionFunctionApp
{
class Startup : FunctionsStartup
{
public override void Configure(IFunctionsHostBuilder builder)
{
var fileInfo = new FileInfo(Assembly.GetExecutingAssembly().Location);
string path = fileInfo.Directory.Parent.FullName;
var config = new ConfigurationBuilder()
.SetBasePath(Environment.CurrentDirectory)
.SetBasePath(path)
.AddJsonFile("local.settings.json", optional: true, reloadOnChange: true)
.AddEnvironmentVariables()
.Build();
var apiConfig = new ApiConfig();
config.Bind(nameof(ApiConfig), apiConfig);
builder.Services.AddSingleton<FileService>();
builder.Services.AddSingleton(apiConfig);
}
}
}
The above code – from line 15 to 25 – takes care of getting the configuration values, if the app runs locally then it loads the local.settings.json, otherwise, it takes the values from the Azure Function Application settings (see Step 7.2)
5.2 Now set the values of TenantId, ClientId & ClientSecret from Step 1; The SiteId correspond to the Document Library where the file will get temporarily uploaded, we will have to GET it using Microsoft Graph Explorer with the following formula:
This is how the local.settings.json looks:
https://graph.microsoft.com/v1.0/sites/{hostname}:/sites/{path}?$select=id
GET => https://graph.microsoft.com/v1.0/sites/myorganization.sharepoint.com?$select=id
GET => https://graph.microsoft.com/v1.0/sites/myorganization.sharepoint.com:/sites/Contoso/Operations/Manufacturing?$select=id
Response =>
{
"@odata.context": "https://graph.microsoft.com/v1.0/$metadata#sites(id)/$entity",
"id": "myorganization.sharepoint.com,74796aa9-17f6-4c09-9b20-1d78bfdcbac4,98f692fe-ea45-423b-8001-0b9c6bb2b50f"
}
What you get back in the id is in this format: {hostname},{spsite.id},{spweb.id}.
What we need is then the {spsite.id} which is 74796aa9-17f6-4c09-9b20-1d78bfdcbac4
Step 6: Create a new function as the Main entry point
Add a new function to your project and name it ConvertToPdf. Select the Http trigger so our function can be called via a http request and pick Authorization level Anonymous so we don’t need to provide any credentials when calling this function; Replace the below code
using Microsoft.AspNetCore.Http;
using Microsoft.AspNetCore.Mvc;
using Microsoft.Azure.WebJobs;
using Microsoft.Azure.WebJobs.Extensions.Http;
using Microsoft.Extensions.Logging;
using System.Threading.Tasks;
namespace PdfConversionFunctionApp
{
public class ConvertToPdf
{
private readonly FileService _fileService;
private readonly ApiConfig _apiConfig;
public ConvertToPdf(FileService fileService, ApiConfig apiConfig)
{
_fileService = fileService;
_apiConfig = apiConfig;
}
[FunctionName("ConvertToPdf")]
public async Task<IActionResult> Run(
[HttpTrigger(AuthorizationLevel.Anonymous, "post", Route = null)] HttpRequest req, ILogger log)
{
if (req.Headers.ContentLength == 0)
{
log.LogInformation("Please provide a file.");
return new BadRequestObjectResult("Please provide a file.");
}
var path = $"{_apiConfig.GraphEndpoint}sites/{_apiConfig.SiteId}/drive/items/";
var fileId = await _fileService.UploadStreamAsync(path, req.Body, req.ContentType);
var pdf = await _fileService.DownloadConvertedFileAsync(path, fileId, "pdf");
await _fileService.DeleteFileAsync(path, fileId);
return new FileContentResult(pdf, "application/pdf");
}
}
}
Step 7: Create a Function App in Azure to host the code and make it available globally
7.1 Go to https://portal.azure.com, then click on Create Function App
7.2 Once the app is provisioned, on the left navigation blade click on Configuration, then New application setting – we will have to add the below application settings which are needed when the app runs from Azure (the values as the same as step 5.2)
7.3 On the Overview section, download the publish profile while clicking on Get publish profile
Step 8: Import the publish profile & deploy using Visual Studio 2019
8.1 Right-click on Visual Studio, then choose Publish, import your publish settings to deploy your app from the file downloaded in the previous step – then deploy.
8.2 If Debugging is needed then we can use the Azure Function App Log Stream Monitoring features.
Step 9: Test using a Console Application c#
9.1 Create a console application and replace the following code.
using System;
using System.IO;
using System.Net;
using PdfConversionFunctionApp;
namespace PdfConversionConsoleApp
{
class Program
{
static void Main(string[] args)
{
string filePathWord = @"C:\Temp\TestDocument.docx";
string filePathOutWord = @"C:\Temp\TestDocument.pdf";
string filePathExcel = @"C:\Temp\TestExcel.xlsx";
string filePathOutExcel = @"C:\Temp\TestExcel.pdf";
bool IsSuccessWord = ConverToPdf(filePathWord, filePathOutWord);
bool IsSuccessExcel = ConverToPdf(filePathExcel, filePathOutExcel);
}
private static bool ConverToPdf(String filePath, String filePathOut)
{
try
{
//string urlLocal = "http://localhost:7071/api/ConvertToPdf";
string urlAzure = "https://graphpdfconverter.azurewebsites.net/api/ConvertToPdf";
HttpWebRequest req = (HttpWebRequest)WebRequest.Create(urlAzure);
req.Method = "POST";
string fileExtension = Path.GetExtension(filePath);
switch (fileExtension)
{
case ".doc":
req.ContentType = "application/msword";
break;
case ".docx":
req.ContentType = "application/vnd.openxmlformats-officedocument.wordprocessingml.document";
break;
case ".xls":
req.ContentType = "application/vnd.ms-excel";
break;
case ".xlsx":
req.ContentType = "application/vnd.openxmlformats-officedocument.spreadsheetml.sheet"; ;
break;
default:
throw new Exception("Only Word & Excel documents are supported by the Converter");
}
Stream fileStream = System.IO.File.Open(filePath, FileMode.Open);
MemoryStream inputStream = new MemoryStream();
fileStream.CopyTo(inputStream);
fileStream.Dispose();
Stream stream = req.GetRequestStream();
stream.Write(inputStream.ToArray(), 0, inputStream.ToArray().Length);
HttpWebResponse res = (HttpWebResponse)req.GetResponse();
//Create file stream to save the output PDF file
FileStream outStream = System.IO.File.Create(filePathOut);
//Copy the responce stream into file stream
res.GetResponseStream().CopyTo(outStream);
//Dispose the input stream
inputStream.Dispose();
//Dispose the file stream
outStream.Dispose();
return true;
}
catch (Exception ex)
{
Console.WriteLine(ex.Message);
}
return false;
}
}
}
9.2 To test and debug locally, Click F5 on the Function App – Visual Studio will provide a POST URL which you can use in the console to run & debug the code.
9.3 To run it from Azure, go to Azure Portal, then open your Azure Function App, on the left navigation blade click on Functions, click on the function name then Get Function Url. Use this URL in the console to convert the document to pdf.
It is important to mention that the Content Type will define the type of docunent to be converted – find the complete list of Common MIME types.
Step 10: Test using Postman
10.1 In Postman, add the Azure Function App Url (see step 9.3).
10.2 On the Header section, add the appropriate MIME Types
10.3 On the Body section, click on Binary and upload a file then click the Send button.
10.4 On successfull request, we can save the converted pdf file.
Summary
As we can see Microsoft Graph allows us to convert easily documents to pdf, that up to 1 million free calls, along with Azure Function it provides the flexibility to use these features anywhere anytime your users want.
Getting the vaccine is not an easy task – either you go to a vaccination center early to get a token or if lucky try to get an available slot in the Cowin site/Aarogya Setu mobile app – this has been the same experience got by friends, relatives, and colleagues across the country.
Therefore using the Co-WIN Public APIs, I decided to provide this web application to help all my fellow citizens to get vaccinated!
Let’s get vaccinated!
This web application looks for the vaccine slot availability in your respective District by selecting the age & available dose criteria – using the Co-WIN Public APIs, for more details about the API, click here
Please note that this web application does NOT book any slot on your behalf whatsoever – it only provides valuable information to help the citizen to select the available center at that point in time.
How it works
The program run in an interval to query the provided Co-WIN Public APIs to look for an available center in your respective District, taking into consideration the age and available dose.
Once the program finds an available center, an email will be sent at the registered email address a complete report with all details which shows all the available centers along with the available dose at that point in time.
It is important to mention that upon receiving the report, it is highly recommended to book the slots on the cowin.gov.in website or using the Aarogya Setu mobile app.