I promised myself regardless of the result between Vietnam and Uzbekistan in the final match of AFC U23 Championship 2018, I would publish my 350-page book I wrote and sold on Amazon market. The eBook has been sold over 60 copies since the release date. For those who don’t know the book, here is the introduction.
After two articles doing some fun with Azure Key Vault REST API and HttpClient, I’ve got some requests to add more things to work with vault, for example listing all existing vaults under a given subscription, or deleting a vault.
In this article, let’s explore all the operations which you can work through Azure Key Vault REST API for Vault.
In previous article, I demonstrated how to use HttpClient to work with Azure Key Vault REST API. With this approach, you shouldn’t worry about your programming language skills. What I meant was that you could even use Python, for instance, to make a HttpClient object and call Azure Key Vault REST API. This approach gives developers more flexibility to work with Microsoft Azure as it does not limit to the platform supportability.
You were learnt by getting started with creating a new key vault which is used to protect your key, secret or certificate. In this article, let’s take some time looking into secret in Azure Key Vault.
Azure Key Vault is not new to Azure developers and architects. It is a cloud-based service to safeguard your sensitive information and crypto implementation and management . Working with Azure Key Vault can be done via Azure Portal, PowerShell or corresponding client libraries. While people may prefer using a specific library (.e.g Azure Key Vault .NET client), I’d prefer practicing with REST API and HttpClient.
Inspired by unclear instruction on using Azure Key Vault REST API, this article is the result of my practice on the REST API and also found some notes around it.
Yesterday I got a question from my team about Azure Application Insights regarding visualizing Application Insights telemetry in Power BI. Even Application Insights provides extremely intuitive dashboard for a variety of metrics, the main reason of using Power BI is to first eliminate Azure Portal access control, and secondly to combine dataset of telemetry and other datasets.
The question drives me to start researching Application Insights and approach to sending telemetry to Power BI. In this article, I’d like to introduce an approach then quickly walk you through steps to build a demonstration.
“Building a mixed cloud model for SharePoint” series is to show you how possible you can deploy SharePoint workload not only by using Azure Compute service but also Platform-as-a-service based such as Azure Active Directory Domain Services (AD DS), Azure SQL Database.
In this article, let’s again have a look the two deployment models for your SharePoint workload on Azure and decision considerations. Make sure you understand that SharePoint workload on Azure is still considered on-premises deployment as we still use Azure Compute to host SharePoint.
If you are running a WordPress blog in a commercial hosting out of Azure, you may run out of disk capacity because commercial hosting don’t often not offer you a good storage. It becomes a challenge if the blog has many contributors writing articles everyday. Such a workload would result to flushing your hosting’s disk. Is there another option to host your image or video out of your hosting?
I got a couple of requests to walk through the possibility to work with Business Connectivity Services (BCS), in SharePoint 2016 with the mixed cloud model in my series. The requests do inspire me to keep digging into the model and write the article.
Followed by the two previous articles, I showed you how to set up Azure AD Domain Service (AD DS) to act as a domain controller in a SharePoint farm. During the setup, we learned some limitations in Azure AD DS (as of this article). One of them that make us feel uncomfortable is the Azure AD’s password synchronization to Azure AD DS.
Part of Azure experiment, one of my colleagues started playing with Azure API Management last week. He was interested with what I introduced about the service, including API gateway, API publishing portal to readable policies to manipulate inbound request before back-end hit. He also loved to work with API call via REST because API is a flexible way of touching Azure resources through pure HTTP request, without installing any specific library.