Category: Uncategorized

Uncategorized

Azure Files shared by VMs in a Dev Team

Roy Kim on Azure, Office 365 and SharePoint

Azure File is a service in Azure Storage Accounts such that I look at it a managed network file share. For a further introduction read Introduction to Azure Files

A practical use case for me in a development team scenario is where each team member has its own or shared Azure Virtual Machine and there is a need to share files. A traditional approach I have seen is using on-premises network file shares.

The type of files one can store are software installation files, scripts, local Git repos, developer and system admin documentation, etc. But I wouldn’t suggest this to be a replacement for project and document management solutions such as SharePoint or TFS.

Other alternative approaches may not feasible such as Dropbox or online cloud drives where they have network policies and security policies that discourage or limit use. Or on-premises network file shares may not be accessible or the…

View original post 320 more words

Uncategorized

Azure Logic Apps for Document Content Approval

Roy Kim on Azure, Office 365 and SharePoint

Logic Apps is an Azure service for enterprise integration. It comes with many connectors including from outside of the Microsoft ecosystem. In this blog post, I will show an implementation and key implementation points that will facilitate an approval process for approving a document in SharePoint Online.

Business Scenario

  1. User publishes a document for approval.
    LogicAppContentApproval3LogicAppContentApproval1
  2. Assigned approver gets an email to either approve or reject
    LogicAppContentApproval2
  3. Document is set as approved or rejected.
    LogicAppContentApproval3

The business process will be integrating the following three Office 365 services.

  • SharePoint Online – Document Library
  • Office 365 User Profile with Email
  • Outlook

The Logic App Design
LogicAppContentApproval4

Implementation Details

  1. To trigger this Logic App, it done through any modification of the document item properties such as the user action of publishing.
  2. We must get the file metadata of the document specifically the ETag which represents the file version. This is for future use. Note this is not…

View original post 345 more words

Uncategorized

2018 Cloud Growth Profiled in RightScale State of the Cloud Report — Build Azure

The last few years, RightScale has been surveying organizations and putting together the annual “State of the Cloud Report”. The survey includes data collected from 997 technical professionals across a broad cross-section of organizations, and focuses on gathering information about their adoption of the Cloud. Some of the metric included in the report show the…

via 2018 Cloud Growth Profiled in RightScale State of the Cloud Report — Build Azure

Uncategorized

Microsoft Redefines Leadership in Top 100 Global Technology Leader list by Thomson Reuters — Build Azure

Thomson Reuters has released their first Top 100 Global Technology Leaders list to define new criteria for determining leadership in the 21st century. They’ve already been tracking tons of metrics on companies all around the world for their clients, and have decided to combine it all to create this new list. Thomson Reuters feels they’ve…

via Microsoft Redefines Leadership in Top 100 Global Technology Leader list by Thomson Reuters — Build Azure

 

Uncategorized

Downloading Microsoft Docs as PDF

Did you know you can download a specific set of docs as a PDF without it taking gigabytes of space, enabling you to take it anywhere with you on your desktop or mobile device.

Simply go to the particular docs you’re interested in, for example the Azure Application Architecture Guide and then below table of contents on the left side you will see a Download PDF button.

image

Clicking the Download PDF button will open up the latest version of the docs for this topic in a browser and from here you can click to save.

image

As you can see it downloaded a 73 page PDF document with all the content found online.

As content is changed online, clicking the Download PDF will result in getting the latest version of this document.

To follow up and learn about other updates to the Microsoft Docs site, follow their blog at https://docs.microsoft.com/en-us/teamblog/.

image

Enjoy!

References

https://docs.microsoft.com/en-us/teamblog/docs-november-update

https://docs.microsoft.com/en-us/teamblog/

https://docs.microsoft.com/en-ca/azure/

Uncategorized

Serverless On-Demand Scaling : Pushing the pedal when you need it…

Karim Vaes

Introduction

A lot of workloads are driven by peak consumption. From my experience, there aren’t the amount of workloads that have a constant performance need are in the minority. Now here comes the interesting opportunity when leveraging serverless architectures… Here you only pay for your actual consumption. So if you tweak your architecture to leverage this, then you can get huge gains!

For today’s post, I’ll be using VMchooser once again as an example. A lot has changed since the last post on the anatomy of this application. Here is an updated drawing of the high level architecture ;

Underneath you can see the flow that’ll be used when doing a “Bulk Mapping” (aka “CSV Upload”). The webapp (“frontend”) will store the CSV as a blob on the storage account. Once a new blob arrives, a function will be triggered that will examine the CSV file and put every entry…

View original post 953 more words

Uncategorized

How to Configure Git in Visual Studio to Prune Branches during a Fetch

If you’ve been using Git from within Visual Studio 2017 you might be aware of the fact that when performing a fetch it would not automatically prune your local list of branches that no longer exist on the server. Typically you would have to open up a Command Prompt and run the following command to cleanup your list of branches that exist on the remote:

> git remote prune origin

image

Well now with Visual Studio 2017 Update 5 you can now configure your global and repository settings to prune your local list of branches on every fetch. Let’s take a look at how you can configure this.

First download and install Visual Studio 2017 Update 5. You can do this from within Visual Studio under the Tools menu:

image

Once you have Visual Studio 2017 Update 5 installed, go to the Team Explorer pane and click on Settings where you can configure your default behavior for your Global and/or Repository Settings:

image

image

Now you can change the setting to prune remote branches on every fetch. In my opinion this should be the default value.

image

Another nice addition to the Git settings in Visual Studio 2017 Update 5 is the ability to Rebase your changes when you pull. I’ll explore that in a future post.

In summary when enabling the prune on every fetch, this means your local list of branches is always up-to-date with the remote. Pruning will cleanup and remove your local tracking branches that no longer exist on the server.

Enjoy!

References

Git Configuration: Configure your default behavior