Microsoft with Azure and M365 expose a huge set of API’s for their products. Picking the right ones to ensure the utmost business value is key in any cloud solution today. Here’s three API’s highlighted in from our solutions.
Microsoft Graph API’s
Connector indexing and search for blog rollup in the intranet.
Azure Cognitive Services – preview
For each pizza order we capture feedback. Collating the sentiment of the feedback is important in order to improve on pizza quality and delivery service. Each order is ran thru a flow to capture the sentiment score.
While we could have called the sentiment API with an out of the box connector we opted to use a custom connector definition in order to call the latest and greatest preview end-point – rumored to be 17% more energy efficient!
Dataverse is the data hub for Pizza Time where everything pizza data is captured and stored in the most secure way.
Showing pizza menu in the ordering apps (PowerApps and Native)
Let’s face it, we all love Microsft (and yes, sometime hates Microsoft, but any type of feeling is a lot better than no feelings!). We use Microsoft technology every day, and of course we use a lot of this in our solution. Let’s go for the one first. Using Power Automate to use data input in Dynamics 365 HR to create a user in Azure AD (I know, you’ve seen this before in a previous post, but it might be easier for you to see everything in one post than for us to reffer to other posts):
Then, why should you leave it up to every employee to create their email signature? Don’t worry, we’ll solve it for you. We’ve created a solution that attach a signature on all outgoing emails that have our company name in Azure AD, configured in the Exchange setup in office365 with data from Azure AD:
And then, the night before a new employee starts at our company, have a Power Automate that imports the user in to Dynamics so that the user can log in to the system. Also, connect the user to the correct worker so that it can access the Employee Self-Service to see and edit data regarding himself:
Power Automate Flow er en kraftfull måte å kombinere businessflyt og integrasjoner med andre systemer. Gjennom å bruke connectorene mot ulike apier, både Microsoft og tredjepart, klarer vi å håndtere notifications, innhenting av brukerdata og utsending av epost i samme logiske flyt.
Når det blir opprettet en ny record i dataverse med sensor data for en enkelt sensor, blir det gjort et HTTPS som starter en ny flyt.
Denne flyten henter først brukerprofilen til en Office365 konto, det blir sendt en e-post til denne kontoen om at en ny trussel er oppdaget på sensor lokasjon (Oslofjorden) også sendes ett dynamisk kort til en chat i Teams.
På det dynamiske kortet har du muligheten til og sende ut Ninja Turtles for og håndtere trusselen. Kortet oppdateres når Ninja Turtles sendes ut.
Her har vi brukt Office365, Outlook, Teams og Dataverse connectoreren. Hver av connectorene kommer som standard-komponenter i PAF og bruker Microsoft sine APIét på baksiden. Dette er til brukerens glede skjult og bruker connection med brukerinnlogging.
The Salespeople get a call from a new customer, they can register a new client using our simple form in SharePoint. The forms have been created using SPFx (SharePoint Framework) with React. The data from the form will then be processed and sent to DataVerse using a Cloud Flow to create a new contact.
When the form is submitted, it creates a record in SharePoint, which we then create a contact in DataVerse with.
When the customer gets created in DataVerse we figured out we want to create a flow that alerts on both email and teams chat when a new customer arrives, this allows our resources to verify the customer and add the customer to our flow.
When a contact record is created, we automatically post a message in teams and send an email to our dedicated email.
Ever wondered where your dog are when there’s no food around? How about asking Cortana, Siri, Alexa, or even better Boten Anna?
We have created an integrated solution, with CI/CD in Azure Devops, Cognitive Services, Azure Functions and Power Virtual Agent.
The solution starts with an Azure Function written in Visual Studio.
When code is completed, committed and Pull Requested into the main branch, our CICD pipeline (YML) fires and pushes the solution to Azure Functions
The Azure function is running with a set of pre-captured surveillance images (Due to GDPR we are not using live video). Each folder consists of three photos, one from the kitchen, one from the hallway and one from the livingroom.
Each of these photos will be evaluated with the cognitive service vision functionality. Each of the evaulated photos will be returned with an url for the user to check, and with a textual answer to where the dog is actually located.
The evaluated images:
With this solution we claim the following badges:
Power User Love – for usage of the Power Virtual Agent
Stairway to Heaven – For the usage of Azure Devops, Azure Functions, Cognitive Service, Azure Storage, Power Virtual Agent
Power of the shell – for the CI/CD YML publishing
The Existential Risk – for usage of AI through Cognitive Service Vision
This is about it, now we have an API exposed through APIM backed by a Function App reacting on HTTPTriggers.
The function app uses the Graph API to read Groups and Members in the Contoso domain from the Slevik Vel dominan.
We are wrapping Groups and Users as Family and Family Members.
The Family Engagement API is available for remote applications and apps that want to develop and use the family engagement platform. As an example: The family engagement web application is intend to use the API to fetch family members and calendar events from the Microsoft Graph API and statistics from The Family Graph API.