Microsoft Azure – Automate Creating, Developing and Deploying Azure Websites

Microsoft Azure is a quick and easy way to create and deploy Web sites or APIs for your cloud consumers. Much has been written on different aspects of Azure Websites, including security, deployment and so on. It’s always a challenge to bring this information into a real-life implementation. In this article, I’ve pulled together these various facets to help you quickly create a production-ready Azure Website. I’ll walk you through the end-to-end lifecycle of creating, deploying, configuring and monitoring an Azure Website.

Refer this MSDN link for more details :

Courtesy : Gyan Jadal

Is it necessary to check out a document in SharePoint ?

Is it necessary to check out a document in SharePoint ?

As you man know, there is a concept of Co-authoring in SharePoint. It allows multiple users to work on the same document simultaneously. The concept of check-in/check-out is a total opposite of co-authoring. In this post, I would like to explain what it is all about and whether you need it at all.

Co-authoring is all about collaboration between multiple users. Check-in/Check-out, on another hand, is a total opposite of co-authoring. Check-in/Check-out is for control freaks like me, who want to control the document they are working on without anyone else messing it up. Essentially, check-out prevents other users from making any changes to the document until you check the document back in.

How to check out a Document?
There are 3 ways for you to check out a document:

  1. Manual check-out
  2. Automatic check-out
  3. Missing required column check-out
  4. Manual Check-out

Manual check-out
To manually check out a document, right-click on the file you want to check out, and choose More > Check-out
check out a document in SharePoint.

Automatic Check-out
Automatic check out means that users will be forced to check out a document from a document library before they can make any edits. To enable automatic check out, go to Library Settings > Versioning Settings and switch Require documents to be checked out before they can be edited? to Yes. Click OK
Next time anyone tries to edit any document in the library – they will be forced to check out a document.

check out a document in SharePoint Message users get when they try to edit (Word) document in the browser.

check out a document in SharePoint Message users get when they try to edit (Word) document using Word desktop application.

Missing Required Column Check-out

This is not really an official name or anything. I call it “a very annoying type of check-out”. It happens when you make your metadata columns required and users upload the file, but exit metadata screen before metadata is filled. SharePoint, in this case, makes the document checked-out. The user then manually needs to fill in required metadata and manually check the file back in. In the meantime, the file will not be visible to anyone else, until the user who is uploading the file fills in the required metadata and checks it in. It is important to note that this type of behavior only occurs in the classic document library. The issue has been addressed with the modern document library. Modern document libraries do not require “required” metadata, so you can upload documents and leave metadata fields blank, and documents will not be checked out by default! Instead, users are able to fill in “required” metadata via a new feature called “attention view”.

check out a document in SharePoint

What Happens when the document is checked out?
Once the document is checked out, there is a little green arrow that appears over the file type icon. If you hover over it with your mouse, it will tell you who the document is checked out to.

What will other users experience?
When you check out a document, users will still be able to access the latest version of the document in SharePoint document library, bit only in Read mode. They will not be able to make any edits or save the document back to the library until the original document is checked back in.

How to check the document back in?
Once you are done with all the changes and are ready to make the document available for others to modify, you can check it back in by choosing Check-in

If you are making changes from within Office Apps, usually it is smart enough to remind you to check in when you exit the application.

Check in on behalf of others
As an Administrator, you can also take over the checked out documents and check them in on other’s behalf. Go to Library Settings, then Manage files which have no checked in version

Then, choose the files you want to take over and choose Take Ownership of Selection

This will allow you to check the file in as if this is your own file (using instructions above).

How to discard check out?
If you wish, you can also discard the check-out altogether. Just choose Discard Check Out from the menu.

Do you need check-in/check out?
Back to the original subject of this post. Do you really need to check out a document before making any changes? Here is my advice:

Try to stay away from the check-out feature unless it is absolutely necessary

For most usual types of document libraries, you do not need to check-out a document or enable automatic check-out. It adds a lot of unnecessary overhead and complexity for end users (i.e. hidden documents). If you have a highly collaborative environment, you do not need to slow the users down by making them check out the file every time they click “Edit”. Moreover, any changes that are made to the document are controlled via version history, so you can always go back and restore a previous version if need be. So to summarize, stay away from check-out, you don’t need.

SPFX: Guide to avoid Common mistakes and pitfalls

While many organizations start working with the SharePoint Framework, they stumble upon many questions ranging from tooling to good practices. To help you get started and avoid common pitfalls, Microsoft put up a guide at

Link : Team-based development on the SharePoint Framework

It’s a must-read for all organizations and don’t hesitate to reach out if you miss anything.

What’s New in SharePoint 2016

1) Hybrid

Microsoft has worked hard to bridge the gap between SharePoint Online and SharePoint On-Premises. Some businesses trust the cloud, while others, for privacy concerns, would rather keep their data on-premises, since they can’t always trust servers to host all their sensitive information.

SharePoint 2016 offers a hybrid feature that allows for the storage of data both on the cloud and on premises. The hybrid installations are now simplified and automated.

2) Hybrid Search

This is possibly the biggest new addition to SharePoint 2016.

The hybrid search offers a unified search experience that runs across SharePoint Online and SharePoint On-Premises for your end users.

Previously, the hybrid setup showed different result lists for SharePoint On-Premises and SharePoint Online on one page, but the results were never organized. Now, you can index all your data and specify what kind of content you would like to search for.

3) Media Preview

SharePoint 2016 also allows you to preview videos and images while hovering over them with your mouse, so you no longer have to click on content to view it.

4) Large Files

Older versions of SharePoint do not support large files; any file larger than 2047 MB will not be uploaded. With the release of SharePoint 2016, the permitted file size has been increased to 10 GB.

However, it’s generally best to avoid storing very large files in SharePoint, as you may get disconnected while uploading them.

5) Complete Privacy

Hacking is a big issue nowadays for companies with sensitive information. With this in mind, Microsoft decided to focus on improving its encryption connections in SharePoint 2016.

SharePoint now supports Transport Layer Security (TLS 1.2), which ensures a greater degree of privacy and data encryption between two communicating apps.

6) Mobile Experience

Accessing SharePoint on a mobile device used to be a nightmare for many due to its lack of responsive design. Fortunately, SharePoint 2016 comes with a user-friendly mobile version featuring excellent design and navigation. Now, you can access SharePoint from anywhere and speak with your team remotely to get work done more easily.

7) Server Roles

The release of SharePoint 2016 came with server role configuration, a feature that allows a SharePoint administrator to assign the role of their choice to a specific SharePoint 2016 server. This enables only the functionalities that you need and ensures that all servers belonging to each role are cooperative. You can also convert servers to serve new roles if needed.

8) Faster Site Creation

SharePoint 2013 used to take over 40 seconds to create a site. With PowerShell configurations, you can now use templates to create site collections within a few seconds, generally improving site performance.

9) Compliance Centre

This feature is essential for controlling the flow of data exposed to the cloud. SharePoint allows you to create your own policies and apply them as needed to your environment.

For example, it offers a feature similar to a retention policy; after a certain number of years, you can delete information from OneDrive for Business sites.

10) App Launcher and Sites in One Place

SharePoint 2016 allows you to view both On-Premises and Office 365 in one location via the App Launcher under the “Sites” app.

The App Launcher provides easy access to Office 365 apps such as Delve, OneDrive, OneNote, and more.

11) Durable Links

Lastly, the links you distribute will remain intact even after a document moves to another location or is renamed.

You can achieve this by using a Resource-ID-based link for documents hosted in SharePoint. You no longer have to search files by name and can just use the resource ID containing the document stored in the database.

These are just a few of the great features Microsoft introduced in SharePoint 2016. Do you have any others you’d like to add? Let us know in the comments.

Windows 10 Hyper-V Property “MaxInternalSize” does not exist in class “Msvm_VirtualHardDiskSettingData”

Be sure you have a good backup before trying any of these steps. They worked for me and the problem I was experiencing – DO NOT use these instructions for any problems other than the one described here.

If you mounted one of your VM’s VHDs and then, after un-mounting it, tried to start it on Windows 10 you will get the error message that the VM failed to change state.

If you attempt to inspect the virtual disk in Hyper-V (or from the Virtual Machine Settings), you will get this error message:

There was a problem with one of the command line parameters. Either ‘YourMachineNameHere’ could not be found, or ‘YourVMDiskPathHere’ is not a valid path.
Property ‘MaxInternalSize’ does not exist in class ‘Msvm_VirtualHardDiskSettingData’.

The solution is to use PowerShell to relink the checkpoint differencing disk with the parent VHD.

First, if you have multiple checkpoints, find out which checkpoint disk (AVHDX) points to the parent VHDX file instead of another AVHDX checkpoint differencing disk.

The simplest way to do this for a small number of snapshots is to use the PowerShell command Get-VHD to list the parent disk for each AVHDX file.

Example output:

PS D:vmsWindows 7 32 SP1Virtual Hard Disks> get-vhd '.Windows 7 32 SP1_14285
ComputerName            : DELL-XPS8700
Path                    : d:vmswindows 7 32 sp1virtual hard diskswindows 7
32 sp1_14285771-a2ec-4596-8ed3-2aa162ec280d.avhdx
VhdFormat               : VHDX
VhdType                 : Differencing
FileSize                : 4194304
Size                    : 68719476736
MinimumSize             : 68719476736
LogicalSectorSize       : 512
PhysicalSectorSize      : 4096
BlockSize               : 2097152
ParentPath              : D:VMsWindows 7 32 SP1Virtual Hard DisksWindows 7
32 SP1.vhdx
DiskIdentifier          : B46EE6F1-46D6-4ED0-BEE8-343509B48C75
FragmentationPercentage :
Alignment               : 1
Attached                : False
DiskNumber              :
Number                  :
So we can see that this is our desired snapshot since ParentPath points to our VHDX file. Read more about Get-VHD here: PowerShell Get-VDH
Next, use Set-VHD to set exactly the same parent disk as we found above.

PS C:WINDOWSsystem32> set-vhd 'd:vmswindows 7 32 sp1virtual hard diskswindows 7
32 sp1_14285771-a2ec-4596-8ed3-2aa162ec280d.avhdx' -ParentPath
"D:VMsWindows 7 32 SP1Virtual Hard DisksWindows 7
32 SP1.vhdx"
If the Ignore ID Mismatch option is not used, you will get the error:

Failed to set new parent for the virtual disk.
There exists ID mismatch between the differencing virtual hard disk and the
parent disk.
Read more about Set-VHD here: PowerShell Set-VHD
Courtsey :