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.
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.
In previous article, you created a SharePoint 2016 virtual machine by given built-in template. You were also introduced about Azure AD DS and joined the virtual machine to your Azure AD DS. Everything you have done so far by only PowerShell. Of course, you can create all resources via Azure Portal. However, such a way takes time and hard to control and organize parameters.
Microsoft Account is considered not an internal account given to Microsoft employee. Microsoft account is associated to external services such as Live Mail, Skype, Xbox or so on. When connecting to Azure AD with Microsoft Account (e.g. LiveID) , you might be get started with Connect-AzureAD to get the tenant ID. Below screen is what you might get.
One of the characteristics of cloud computing is agility. Agility means how rapidly you can provision cloud resources and how quickly you can change to meet a scale need. In the context of infrastructure provisioning, you sometimes choose a wrong VM size for your application. Another case when the changing need exists is to scale down the infrastructure when you want to release resources. Saying your e-commerce only needs to be boosted during a specific marketing campaign. After the campaign ends, you need to change the size back to origin to save cost.
One of my Azure security related articles provided step-by-step guidance on how to use Azure Automation with Desired State Configuration (DSC) to deploy security policy on multiple Azure VMs. Instead of clear explanation, the article was just written in a format of step-by-step. Hence, I’ve received some requests to elaborate more about this article so it is fully useful to readers. If you haven’t had a chance to read the article, here you go.