FEED Validator

for Atom and RSS and KML

Congratulations!

This is a valid RSS feed.

Recommendations

This feed is valid, but interoperability with the widest range of feed readers could be improved by implementing the following recommendations.

Your feed appears to be encoded as "utf-8", but your server is reporting "US-ASCII" [help]
line 2, column 0: The prefix "atom" generally is associated with the namespace "http://www.w3.org/2005/Atom" [help]
```
<rss xmlns:atom="https://www.w3.org/2005/Atom" xmlns:sy="https://purl.org/rs ...
```
line 2, column 0: The prefix "sy" generally is associated with the namespace "http://purl.org/rss/1.0/modules/syndication/" [help]
```
<rss xmlns:atom="https://www.w3.org/2005/Atom" xmlns:sy="https://purl.org/rs ...
```
line 2, column 0: The prefix "dc" generally is associated with the namespace "http://purl.org/dc/elements/1.1/" [help]
```
<rss xmlns:atom="https://www.w3.org/2005/Atom" xmlns:sy="https://purl.org/rs ...
```
line 2, column 0: The prefix "content" generally is associated with the namespace "http://purl.org/rss/1.0/modules/content/" [help]
```
<rss xmlns:atom="https://www.w3.org/2005/Atom" xmlns:sy="https://purl.org/rs ...
```
line 2, column 0: The prefix "wfw" generally is associated with the namespace "http://wellformedweb.org/CommentAPI/" [help]
```
<rss xmlns:atom="https://www.w3.org/2005/Atom" xmlns:sy="https://purl.org/rs ...
```
line 2, column 0: The prefix "slash" generally is associated with the namespace "http://purl.org/rss/1.0/modules/slash/" [help]
```
<rss xmlns:atom="https://www.w3.org/2005/Atom" xmlns:sy="https://purl.org/rs ...
```
line 461, column 2: Missing atom:link with rel="self" [help]
```
  </channel>
  ^
```

Source: https://blogs.msdn.microsoft.com/paraspatidar/feed/

<?xml version="1.0" encoding="utf-8"?>
<rss xmlns:atom="https://www.w3.org/2005/Atom" xmlns:sy="https://purl.org/rss/1.0/modules/syndication/" xmlns:dc="https://purl.org/dc/elements/1.1/" xmlns:content="https://purl.org/rss/1.0/modules/content/" xmlns:wfw="https://wellformedweb.org/CommentAPI/" xmlns:slash="https://purl.org/rss/1.0/modules/slash/"
version="2.0">
<channel>
<title>Tomorrow's Technology , Learning Today by Paras Patidar</title>
<atom:link
href="https://docs.microsoft.com/archive/blogs/paraspatidar/feed.xml"
rel="self"
type="application/rss+xml" />
<link>https://docs.microsoft.com/archive/blogs/paraspatidar/feed.xml</link>
<description>_________________ Now , You know it ;)</description>
<lastBuildDate>Wed, 17 Apr 2019 04:06:51 GMT</lastBuildDate>
<language>en-US</language>
<sy:updatePeriod>hourly</sy:updatePeriod>
<sy:updateFrequency>1</sy:updateFrequency>
<item>
<title>Debug .Net Core Application in Local Kubernetes Container with Azure Draft and VS code –Part - 1</title>
<link>https://docs.microsoft.com/archive/blogs/paraspatidar/debug-net-core-application-in-kubernetes-container-with-azure-draft-and-vs-code</link>
<pubDate>Wed, 19 Sep 2018 13:15:19 GMT</pubDate>
<dc:creator><![CDATA[ParasPatidar]]></dc:creator>
<guid
isPermaLink="false">https://blogs.msdn.microsoft.com/paraspatidar/?p=1315</guid>
<description><![CDATA[Two different worlds talk to each other when we go for this topic of debugging dot net core based...]]></description>
<content:encoded><![CDATA[ Two different worlds talk to each other when we go for this topic of debugging dot net core based sample application which is basically a containerized application  using VS code with help of Azure Draft.The two different worlds : Kubernetes  - Black world of command prompt.VS code – that colorful (blue tough) , UI. This article shows how to combine these two different worlds to enable debugging your Dot net core based application.This article will take you through step by step with following major section and sub sections :<ol><li>Install required tools and utilities :</li><ul><li>Install docker for windows.</li><li>Install Minikube ( for  Kubernetes ) on windows.</li><li>Install Kubectl , which is CLI for Kubernetes .</li><li>Install VS code.</li><li>Install Helm.</li><li>Install Azure Draft.</li></ul><li>Create Sample dot net core app in visual studio and setup draft.</li><li>Debug the application using draft.</li></ol> Basically what is going to be here is nothing new , the concept of debugging any remotely deployed application are going to apply here.If we remember old days where we want to debug any product deployed application or any application at remote computer then we used to follow following steps :<ol><li>deploy application in Debug mode.</li><li>have MSVSMON.exe available on remote computer up and running .</li><li>connect to that remote computer from our local machine’s visual studio.</li><li>attach the debugger to remote process.</li></ol>Similar things will happen here once we go through all the steps  , using draft here is what happens :<ol>
<li>deploy application in Debug mode in local minikube node as container application  .</li>
<li>have VSDBG package available on container (that will be done automatically once we setup sample application for draft DokerFile)</li>
<li>connect to that container  from VS code by using launch.json setting of VS code.
</li>
<li>attach the debugger to remote process that will be done once we hit the debug button using that specific launch setting.</li></ol> ]]></content:encoded>
</item>
<item>
<title>Where are New Posts ? birth of “blog.paraspatidar.com”</title>
<link>https://docs.microsoft.com/archive/blogs/paraspatidar/where-are-new-posts-birth-of-blog-paraspatidar-com</link>
<pubDate>Mon, 04 Jun 2018 20:00:43 GMT</pubDate>
<dc:creator><![CDATA[ParasPatidar]]></dc:creator>
<guid
isPermaLink="false">https://blogs.msdn.microsoft.com/paraspatidar/?p=1295</guid>
<description><![CDATA[Dear Readers,As a part of continuing the professional  journey and enthusiasms toward new...]]></description>
<content:encoded><![CDATA[ Dear Readers,As a part of continuing the professional  journey and enthusiasms toward new challenges , I have move on and have been separated from my organization Microsoft.However , I shall keep exploring the ocean of technology and will keep writing the content which is useful for every technology lover.My Future post will be available at : <a href="https://blog.paraspatidar.com/">https://blog.paraspatidar.com/</a>Or at<a href="https://paraspatidar.com/blog">https://paraspatidar.com/blog</a>It will take me some time to setup new blog and contain and thus temporarily links might redirect to my personal web site <a href="https://paraspatidar.com/">https://paraspatidar.com/</a>& my GitHub profile :<a title="https://github.com/paraspatidar" href="https://github.com/paraspatidar">https://github.com/paraspatidar</a> Stay in touch & enjoy innovating . Thanks,Paras Patidar]]></content:encoded>
</item>
<item>
<title>Web App Instance Name and ARR affinity Mapping using Function App – Part-5</title>
<link>https://docs.microsoft.com/archive/blogs/paraspatidar/web-app-instance-name-and-arr-affinity-mapping-using-function-app-part-5</link>
<pubDate>Thu, 24 May 2018 00:14:11 GMT</pubDate>
<dc:creator><![CDATA[ParasPatidar]]></dc:creator>
<guid
isPermaLink="false">https://blogs.msdn.microsoft.com/paraspatidar/?p=1255</guid>
<description><![CDATA[This Post is in continuation of Post :Web App Instance Name and ARR affinity Mapping using...]]></description>
<content:encoded><![CDATA[<hr>
This Post is in continuation of Post :<a href="https://blogs.msdn.microsoft.com/paraspatidar/web-app-instance-name-and-arr-affinity-mapping-using-function-app-part-4/">Web App Instance Name and ARR affinity Mapping using Function App – Part-4</a>
as Part 5  Our next step is
Deploy the Function App code & Test It section :     

11. Download the function app from my GitHub Profile.


<ul>
<li>You can select Powershell based Function code from here : <a title="https://github.com/paraspatidar/Code-Dump/blob/master/FnInstanceARRMapper.ps1" href="https://github.com/paraspatidar/Code-Dump/blob/master/FnInstanceARRMapper.ps1">https://github.com/paraspatidar/Code-Dump/blob/master/FnInstanceARRMapper.ps1</a>
</li>
<li>You can select C# based Function which will work as precompiled code from here : <a title="https://github.com/paraspatidar/Code-Dump/blob/master/InstanceARRMapping.zip" href="https://github.com/paraspatidar/Code-Dump/blob/master/InstanceARRMapping.zip">https://github.com/paraspatidar/Code-Dump/blob/master/InstanceARRMapping.zip</a>
</li>
</ul>
        it will be good idea to keep the function access level as anonymous by not using any key (function key / master key)  , you can handle it in Integrate option of function app. 

12 .Based on function app  (Powershell or C# based) , accordingly choose the URL and pass-on any Web App’s name & its resource group Name which is up and running in your subscription in the   Query string / URL .        
        the URL for both type of function will be little different and it is mentioned in source code itself . Feel free to modify the code and change according to your convenience. 
 

13 .Receive the response with Instance name & ARRAffinity mapping 
 
<ul>
<li> Testing C# Based Function App : sample URL is in project code  file </li>
</ul>
<div class="paraBelow">
<a href="https://msdnshared.blob.core.windows.net/media/2018/05/image259.png">
<img width="575" height="161" title="image" alt="image" src="https://msdnshared.blob.core.windows.net/media/2018/05/image_thumb199.png" border="0">
</a>
</div>
<ul>
<li> Testing Powershell Based Function App :sample URL is in code  file </li>
</ul>
<div class="paraBelow">
<a href="https://msdnshared.blob.core.windows.net/media/2018/05/image260.png">
<img width="578" height="90" title="image" alt="image" src="https://msdnshared.blob.core.windows.net/media/2018/05/image_thumb200.png" border="0">
</a>
</div>
<div class="paraBelow"> </div>
<div class="paraBelow">As the number of instances grow  , the time to get response will also increase , however , in C# based function app we have tried to use Async calls but still has scope for further improvement , please feel free to use the code as per requirement. </div>
<div class="paraBelow"> </div>
<div class="paraBelow"> </div>]]></content:encoded>
</item>
<item>
<title>Web App Instance Name and ARR affinity Mapping using Function App – Part-4</title>
<link>https://docs.microsoft.com/archive/blogs/paraspatidar/web-app-instance-name-and-arr-affinity-mapping-using-function-app-part-4</link>
<pubDate>Wed, 23 May 2018 22:53:45 GMT</pubDate>
<dc:creator><![CDATA[ParasPatidar]]></dc:creator>
<guid
isPermaLink="false">https://blogs.msdn.microsoft.com/paraspatidar/?p=1155</guid>
<description><![CDATA[This Post is in continuation of Post :Web App Instance Name and ARR affinity Mapping using Function...]]></description>
<content:encoded><![CDATA[This Post is in continuation of Post :<a href="https://blogs.msdn.microsoft.com/paraspatidar/web-app-instance-name-and-arr-affinity-mapping-using-function-app-part-3/">Web App Instance Name and ARR affinity Mapping using Function App – Part-3</a>as Part 4  Our next step is Creating a blank Function app and add application settings section :7. Note down Subscription id and Tenant Id from Azure Portal.
When programmatically logging in, you need to pass the tenant ID with your authentication request.<ul><li>Select Azure Active Directory.<img alt="select azure active directory" src="https://docs.microsoft.com/en-us/azure/azure-resource-manager/media/resource-group-create-service-principal-portal/select-active-directory.png"><li>To get the tenant ID, select Properties for your Azure AD tenant.<img alt="select Azure AD properties" src="https://docs.microsoft.com/en-us/azure/azure-resource-manager/media/resource-group-create-service-principal-portal/select-ad-properties.png"><li>Copy the Directory ID. This value is your tenant ID.<img alt="tenant ID" src="https://docs.microsoft.com/en-us/azure/azure-resource-manager/media/resource-group-create-service-principal-portal/copy-directory-id.png"></li><li>On Azure portal , click on subscription option in left and Note the subscription Id details under which we have assigned the Service principal in last post and we shall be able to get the Web App instance details which are created in this subscription only.</li></ul>           <a href="https://msdnshared.blob.core.windows.net/media/2018/05/image254.png"><img width="838" height="411" title="image" alt="image" src="https://msdnshared.blob.core.windows.net/media/2018/05/image_thumb194.png" border="0"></a> 8. Create a new Function App.
refer this link to create a function app in Azure : <a title="https://docs.microsoft.com/en-us/azure/azure-functions/functions-create-function-app-portal#create-a-function-app" href="https://docs.microsoft.com/en-us/azure/azure-functions/functions-create-function-app-portal#create-a-function-app">https://docs.microsoft.com/en-us/azure/azure-functions/functions-create-function-app-portal#create-a-function-app</a> one the function app is created , go to Function apps option on left hand side of Azure portal to open that function app and then select the Application setting to create the various application setting :<a href="https://msdnshared.blob.core.windows.net/media/2018/05/image255.png"><img width="855" height="419" title="image" alt="image" src="https://msdnshared.blob.core.windows.net/media/2018/05/image_thumb195.png" border="0"></a> 9. Create Application settings for : Subscription id ,  Tenant Id  , Application Id & Client Secret. <a href="https://msdnshared.blob.core.windows.net/media/2018/05/image256.png"><img width="822" height="185" title="image" alt="image" src="https://msdnshared.blob.core.windows.net/media/2018/05/image_thumb196.png" border="0"></a>Here like we discussed :AADApplicationId is same as Service Principal Id also known as Client ID , which is nothing but AAD application’s Application Id.AADApplicationKey is same as Client Secret which is the Key which you have created in previous post for AAD application. Please note , the Github code in Function app is written to read these app setting keys , if you write different  app setting key names ,then you will need to modify that code as well to read those keys , otherwise you will end up getting no key and thus runtime exception. Now in Next Post we will go through  Deploy the Function App code & Test It section here : <a href="https://blogs.msdn.microsoft.com/paraspatidar/web-app-instance-name-and-arr-affinity-mapping-using-function-app-part-5/">Web App Instance Name and ARR affinity Mapping using Function App – Part-5</a>]]></content:encoded>
</item>
<item>
<title>Web App Instance Name and ARR affinity Mapping using Function App – Part-3</title>
<link>https://docs.microsoft.com/archive/blogs/paraspatidar/web-app-instance-name-and-arr-affinity-mapping-using-function-app-part-3</link>
<pubDate>Wed, 23 May 2018 22:25:59 GMT</pubDate>
<dc:creator><![CDATA[ParasPatidar]]></dc:creator>
<guid
isPermaLink="false">https://blogs.msdn.microsoft.com/paraspatidar/?p=1085</guid>
<description><![CDATA[This Post is in continuation of Post :Web App Instance Name and ARR affinity Mapping using Function...]]></description>
<content:encoded><![CDATA[ This Post is in continuation of Post :<a href="https://blogs.msdn.microsoft.com/paraspatidar/web-app-instance-name-and-arr-affinity-mapping-using-function-app-part-2/">Web App Instance Name and ARR affinity Mapping using Function App – Part-2</a>as Part 3  Our next step is Creating and Setting up Service Principal  (AAD Application ) :Creating and Setting up Service Principal  (AAD Application ) :<ol><li>Creating Azure AAD App aka Service Principal.
<li>Noting down the Application Id of AAD app which is also known as Client Id or Service Principal Id<li>Generating Key for that AAD app , which is knows as  Client Secret or Password.<li>Assigning Reader role on subscription to  that service principal (AAD App)  so that it can read the resources of subscription and query ARM endpoints .</li></ol>We can cover the above mentioned steps  using the Microsoft well explanatory document here : <a title="https://docs.microsoft.com/en-us/azure/azure-resource-manager/resource-group-create-service-principal-portal" href="https://docs.microsoft.com/en-us/azure/azure-resource-manager/resource-group-create-service-principal-portal">https://docs.microsoft.com/en-us/azure/azure-resource-manager/resource-group-create-service-principal-portal</a>But for the sack of completeness , let me try giving and high level step overview here itself :1. Creating Azure AAD App aka Service Principal<ul><li>Log in to your Azure Account through the <a href="https://portal.azure.com/">Azure portal</a>.
<li>Select Azure Active Directory.<img alt="select azure active directory" src="https://docs.microsoft.com/en-us/azure/azure-resource-manager/media/resource-group-create-service-principal-portal/select-active-directory.png"><li>Select App registrations.<img alt="select app registrations" src="https://docs.microsoft.com/en-us/azure/azure-resource-manager/media/resource-group-create-service-principal-portal/select-app-registrations.png"><li>Select New application registration.<img alt="add app" src="https://docs.microsoft.com/en-us/azure/azure-resource-manager/media/resource-group-create-service-principal-portal/select-add-app.png"><li>Provide a name and URL for the application. Select Web app / API for the type of application you want to create. You cannot create credentials for a <a href="https://docs.microsoft.com/en-us/azure/active-directory/manage-apps/application-proxy-configure-native-client-application">Native application</a>; therefore, that type does not work for an automated application. After setting the values, select Create.<img alt="name application" src="https://docs.microsoft.com/en-us/azure/azure-resource-manager/media/resource-group-create-service-principal-portal/create-app.png"></li></ul>You have created your application. <h4>2. Noting down the Application Id of AAD app which is also known as Client Id or Service Principal Id</h4> When programmatically logging in, you need the ID for your application and an authentication key. To get those values, use the following steps:<ul><li>From App registrations in Azure Active Directory, select your application.<img alt="select application" src="https://docs.microsoft.com/en-us/azure/azure-resource-manager/media/resource-group-create-service-principal-portal/select-app.png"><li>Copy the Application ID and store it in your application code. Some <a href="https://docs.microsoft.com/en-us/azure/azure-resource-manager/resource-group-create-service-principal-portal#log-in-as-the-application">sample applications</a> refer to this value as the client ID.<img alt="client ID" src="https://docs.microsoft.com/en-us/azure/azure-resource-manager/media/resource-group-create-service-principal-portal/copy-app-id.png"></li></ul> 3. Generating Key for that AAD app , which is knows as  Client Secret or Password.<ul><li>To generate an authentication key, select Settings.<img alt="select settings" src="https://docs.microsoft.com/en-us/azure/azure-resource-manager/media/resource-group-create-service-principal-portal/select-settings.png"><li>To generate an authentication key, select Keys.<img alt="select keys" src="https://docs.microsoft.com/en-us/azure/azure-resource-manager/media/resource-group-create-service-principal-portal/select-keys.png"><li>Provide a description of the key, and a duration for the key. When done, select Save.<img alt="save key" src="https://docs.microsoft.com/en-us/azure/azure-resource-manager/media/resource-group-create-service-principal-portal/save-key.png">After saving the key, the value of the key is displayed. Copy this value because you are not able to retrieve the key later. You provide the key value with the application ID to log in as the application. Store the key value where your application can retrieve it.<img alt="saved key" src="https://docs.microsoft.com/en-us/azure/azure-resource-manager/media/resource-group-create-service-principal-portal/copy-key.png"></li></ul> 4. Assigning Reader role on subscription to  that service principal (AAD App)  To access resources in your subscription, you must assign the application to a role. Decide which role represents the right permissions for the application. To learn about the available roles, see <a href="https://docs.microsoft.com/en-us/azure/role-based-access-control/built-in-roles">RBAC: Built in Roles</a>.You can set the scope at the level of the subscription, resource group, or resource. Permissions are inherited to lower levels of scope. For example, adding an application to the Reader role for a resource group means it can read the resource group and any resources it contains.<ul><li>Navigate to the level of scope you wish to assign the application to. For example, to assign a role at the subscription scope, select Subscriptions. You could instead select a resource group or resource.<img alt="select subscription" src="https://docs.microsoft.com/en-us/azure/azure-resource-manager/media/resource-group-create-service-principal-portal/select-subscription.png"><li>Select the particular subscription (resource group or resource) to assign the application to.<img alt="select subscription for assignment" src="https://docs.microsoft.com/en-us/azure/azure-resource-manager/media/resource-group-create-service-principal-portal/select-one-subscription.png"><li>Select Access Control (IAM).<img alt="select access" src="https://docs.microsoft.com/en-us/azure/azure-resource-manager/media/resource-group-create-service-principal-portal/select-access-control.png"><li>Select Add.<img alt="select add" src="https://docs.microsoft.com/en-us/azure/azure-resource-manager/media/resource-group-create-service-principal-portal/select-add.png"><li>Select the role you wish to assign to the application. The following image shows the Reader role.<img alt="select role" src="https://docs.microsoft.com/en-us/azure/azure-resource-manager/media/resource-group-create-service-principal-portal/select-role.png"><li>By default, Azure Active Directory applications aren't displayed in the available options. To find your application, you must provide the name of it in the search field. Select it.<img alt="search for app" src="https://docs.microsoft.com/en-us/azure/azure-resource-manager/media/resource-group-create-service-principal-portal/search-app.png"><li>Select Save to finish assigning the role. You see your application in the list of users assigned to a role for that scope.</li></ul>Now in Next Post we will go through  Creating a blank Function app and add application settings section here : <a href="https://blogs.msdn.microsoft.com/paraspatidar/web-app-instance-name-and-arr-affinity-mapping-using-function-app-part-4/">Web App Instance Name and ARR affinity Mapping using Function App – Part-4</a>]]></content:encoded>
</item>
<item>
<title>Web App Instance Name and ARR affinity Mapping using Function App – Part-2</title>
<link>https://docs.microsoft.com/archive/blogs/paraspatidar/web-app-instance-name-and-arr-affinity-mapping-using-function-app-part-2</link>
<pubDate>Wed, 23 May 2018 22:08:37 GMT</pubDate>
<dc:creator><![CDATA[ParasPatidar]]></dc:creator>
<guid
isPermaLink="false">https://blogs.msdn.microsoft.com/paraspatidar/?p=1075</guid>
<description><![CDATA[    This Post is in continuation of Post :Web App Instance Name and ARR affinity...]]></description>
<content:encoded><![CDATA[    This Post is in continuation of Post :<a href="https://blogs.msdn.microsoft.com/paraspatidar/web-app-instance-name-and-arr-affinity-mapping-using-function-app-part1/" target="_blank" rel="noopener">Web App Instance Name and ARR affinity Mapping using Function App – Part-1</a> as Part 2  Our next step is Outlining the things which we need to do:
 
Here are few things which we shall be doing step by step in upcoming post 
Steps summary:
Creating and Setting up Service Principal  (AAD Application ) :
<ol>
<li>Creating Azure AAD App aka Service Principal.</li><li>Noting down the Application Id of AAD app which is also known as Client Id or Service Principal Id</li>
<li>Generating Key for that AAD app , which is knows as  Client Secret or Password.</li>
<li>Assigning Reader role on subscription to  that service principal (AAD App)  so that it can read the resources of subscription and query ARM endpoints .</li></ol>Creating a blank Function app and add application settings section entries.<ol start="7">
<li>Note down Subscription id and Tenant Id from Azure Portal.</li><li>Create a new Function App.</li><li>Create Application settings for : Subscription id ,  Tenant Id  , Application Id & Client Secret.</li></ol> Deploy the Function App code & Test It:
<ol start="11">
<li>Download the function app from my GitHub Profile.</li>
<li>Based on function app  (powershell or C# based) , accordingly choose the URL and pass-on any Web App’s name & its resource group Name which is up and running in your subscription in the   Query string / URL .</li>
<li>Receive the response with Instance name & ARRAffinity mapping .</li>
</ol>
 <ol start="20">
</ol>

So if are excited about this automation ,then continue further part in  my next Post here : 
<a href="https://blogs.msdn.microsoft.com/paraspatidar/web-app-instance-name-and-arr-affinity-mapping-using-function-app-part-3/" target="_blank" rel="noopener">Web App Instance Name and ARR affinity Mapping using Function App – Part-3</a>]]></content:encoded>
</item>
<item>
<title>Web App Instance Name and ARR affinity Mapping using Function App – Part-1</title>
<link>https://docs.microsoft.com/archive/blogs/paraspatidar/web-app-instance-name-and-arr-affinity-mapping-using-function-app-part1</link>
<pubDate>Wed, 23 May 2018 21:23:22 GMT</pubDate>
<dc:creator><![CDATA[ParasPatidar]]></dc:creator>
<guid
isPermaLink="false">https://blogs.msdn.microsoft.com/paraspatidar/?p=1045</guid>
<description><![CDATA[Goal of this Post :
in this post we shall...]]></description>
<content:encoded><![CDATA[

Goal of this Post :


<div class="paraBelow">
in this post we shall discuss on some one time activity on your azure portal , which will finally create a Http trigger based Function app   with an URL.
once that is done , passing any web app name & resource group name to that URL will return all running instances of web application as well as their ARRAffinity  Id , so anyone can query this read-only data from any device which is capable of making normal HTTP call , thus any computing device limitation , any script limitation , any manual effort is gone.
</div>
 
As we all know that Azure App Services uses sticky session by default in case of multiple instance (i.e. load balancing between multiple VM which are running your web application) ,  those sticky session are maintained by a cookie key named ARRAffinity .
for all the running instances , there is is this unique value and based on this cookie value , browser’s request is redirected to specific instance.
While instances(VMs) has some standard name like : RD00XXXXXXX  , ARRAffinity  is some random alphanumeric 
you can delete these cookie key and try to connect to web app by refreshing url again , you will randomly get any of the ARRAffinity  key and your browser request will connect to the instance associated with that ARRAffinity.


<a href="https://msdnshared.blob.core.windows.net/media/2018/05/image253.png">
<img width="630" height="362" title="image" class="shadow" alt="image" src="https://msdnshared.blob.core.windows.net/media/2018/05/image_thumb193.png" border="0">
</a>

 
However In day to day app service maintenance and troubleshooting related issue , we may have requirement to connect to only any specific instance , for example manipulating anything on that instance only , Getting memory dump from that instance , killing any specific process on any particular instance  and lot many other requirements.
This requirement has two major challenges :
1. Identifying ARRAffinity cookie for any specific instance .2. Once we know that ARRAffinity  , then using various available options , connect to that specific instance.Lets discuss about both these challenges :


 Identifying ARRAffinity cookie for any specific instance  :

<div class="paraBelow">
     There is no out of the box UI  available to get the ARRAffinity of any specific instance  , but here are some options :
<ul>
<li>Using steps mentioned in this blog post , you can get all ARRAffinity  , but not the instance name so you may try connecting all those instances one by one to verify which one is of your interest :</li>
</ul>
           <a title="https://blogs.msdn.microsoft.com/kaushal/2016/11/21/azure-app-service-how-to-connect-to-the-kudu-site-of-a-specific-instance/" href="https://blogs.msdn.microsoft.com/kaushal/2016/11/21/azure-app-service-how-to-connect-to-the-kudu-site-of-a-specific-instance/">https://blogs.msdn.microsoft.com/kaushal/2016/11/21/azure-app-service-how-to-connect-to-the-kudu-site-of-a-specific-instance/</a>
           many hits & trials involved to reach to correct Instance …so lets move to next way 
<ul>
<li>Using a Powershell  <a href="https://github.com/paraspatidar/Code-Dump/blob/master/InstanceName_ArrAffinityCombination.ps1" target="_blank">script located here</a> , you can get the list of Instance name with their ARRAffinity  value , but this has the limitation that :</li>
<ul>
<li>you must run this script every time you want to find the information </li>
<li> login with your account  </li>
<li>you must be on a machine capable to run PowerShell script and of course </li>
<li> you need that powershell script handy</li>
</ul>
</ul>
           …………….phew………
</div>
 


Connect to that specific instance.

<div class="paraBelow">
<ul>
<li>Using Browser extension to edit the cookie , once we know the ARRAffinity   ,  we can connect to specific instance by using recommendation as in this post : <a title="https://blogs.msdn.microsoft.com/kaushal/2016/11/21/azure-app-service-how-to-connect-to-the-kudu-site-of-a-specific-instance/" href="https://blogs.msdn.microsoft.com/kaushal/2016/11/21/azure-app-service-how-to-connect-to-the-kudu-site-of-a-specific-instance/">https://blogs.msdn.microsoft.com/kaushal/2016/11/21/azure-app-service-how-to-connect-to-the-kudu-site-of-a-specific-instance/</a> </li>
<li>Using some Azure App Service extension like Instance Detective by  <a href="https://github.com/nmallick1/MutliConsoleExt" target="_blank">Nazeef Mallick</a> , which will help you to directly connect to any specific instance , but only issue is :</li>
<ul>
<li>you need to instance this extension to some site </li>
<li>you should have KUDU access for that site</li>
<li>you should have publish profile handy for the app service for which you want to connect to particular instance.</li>
</ul>
</ul>
          If above 3 challenges are not the concern , then I would recommend to use above extension , but if you are looking for some automated way where you don't need to do anything manual to find ARRAffinity    & Instance name combination , then this Post is for you.

</div>
So if are excited about this automation ,then continue further part in  my next Post here : 
<a href="https://blogs.msdn.microsoft.com/paraspatidar/web-app-instance-name-and-arr-affinity-mapping-using-function-app-part-2/" target="_blank" rel="noopener">Web App Instance Name and ARR affinity Mapping using Function App – Part-2</a>


]]></content:encoded>
</item>
<item>
<title>Using SMO on Azure App Service (Web Apps) with Azure SQL DB</title>
<link>https://docs.microsoft.com/archive/blogs/paraspatidar/using-smo-on-azure-app-service-web-apps-with-azure-sql-db</link>
<pubDate>Sat, 10 Mar 2018 12:31:09 GMT</pubDate>
<dc:creator><![CDATA[ParasPatidar]]></dc:creator>
<guid
isPermaLink="false">https://blogs.msdn.microsoft.com/paraspatidar/?p=985</guid>
<description><![CDATA[SQL server management object SMO) is one of the widely used way to interact with SQL server due to...]]></description>
<content:encoded><![CDATA[SQL server management object SMO) is one of the widely used way to interact with SQL server due to its feature for directly able to execute mass operation as well as management operation on SQL server, instead of old school way of using queries.
However when using it , it should also need to be consider that on the environment where we are using it is compatible in various aspects or not.
If you have been using existing SMO based project and moving on to Azure App services & facing any issue post deployment in SMO calls.
Or
You are building your application from scratch and planning to deploy it on Azure App services, there here are few things which you should do :
1. Correct Way of Using SMO DLL/Objects :
You should refer to this link, and use the SMO Nuget package to get the SMO dll and create object out of it :
<a href="https://www.nuget.org/packages/Microsoft.SqlServer.SqlManagementObjects">https://www.nuget.org/packages/Microsoft.SqlServer.SqlManagementObjects</a>
 
<a href="https://msdnshared.blob.core.windows.net/media/2018/03/clip_image00211.jpg"><img width="649" height="77" title="clip_image002" alt="clip_image002" src="https://msdnshared.blob.core.windows.net/media/2018/03/clip_image002_thumb10.jpg" border="0" /></a>
 
2. Connecting to on-Prem SQL database :
To Connect to on-Prem database , you don’t need to do anything explicit in code .By using any of the Network connection method like hybrid connection or Vnet , you will be able to connect your web application on On-Prem SQL database and should be able execute most of the SMO operations.
 
3. Connecting to Azure SQL database :
If you are making a connection with Azure SQL database , then you are not explicitly creating any Vnet or Network connection to connect to Azure SQL database , thus here are few things which you should remember :
(1) Try running same code and application from local machine (visual studio) and see if you are able to perform desired operations , if you can execute the same on local machine but having issue in App service , then move further , else try making your code to work with Azure SQL database.
(2) If your code is working fine in local but having issue on Azure App service , there here are few scenarios which can happen :
· Make sure that You have allowed Azure Service in Firewall setting of Azure SQL database:
<a href="https://msdnshared.blob.core.windows.net/media/2018/03/image119.png"><img width="624" height="443" title="image" alt="image" src="https://msdnshared.blob.core.windows.net/media/2018/03/image_thumb107.png" border="0" /></a>
 
· The Calls which you are making may be restricted by Azure App service due to Sandbox environment :
To test it , try changing SQL connection to On-Prem SQL database and create hybrid connection with On-Prem machine and see now if the App service is running fine and executing SQL operation.
<a href="#Interesting" id="Interesting">Interesting things happening here :</a>
The very interesting thing here can bee is that App services being a PaaS environment, runs in a security restricted mode named SandBox and thus it banes some calls for various system , graphics or security related operations.
Read more about sandbox restrictions here
<a href="https://github.com/projectkudu/kudu/wiki/Azure-Web-App-sandbox#app-service-plans-and-sandbox-limits">https://github.com/projectkudu/kudu/wiki/Azure-Web-App-sandbox#app-service-plans-and-sandbox-limits</a>
For example , below is a sample code which runs fine when connecting to on-Prem SQL database form Azure App service.
It also runs fine when connecting to Azure SQL database while running code locally.
So you might endup in a confusion , that why the code is not working with Azure SQL db & Azure App service combination .
 
<a href="https://msdnshared.blob.core.windows.net/media/2018/03/image121.png"><img width="558" height="406" title="image" class="shadow" alt="image" src="https://msdnshared.blob.core.windows.net/media/2018/03/image_thumb109.png" border="0" /></a>
Here is the piece of code emitting above behavior :
<div class="code" style="width: 80%"><script src="https://gist.github.com/paraspatidar/2a398e8f588459c719983e495b65b366.js"></script></div>
<div class="code" style="width: 80%"></div>
In above code, if you look at the line :
<div class="code" style="width: 80%"><script src="https://gist.github.com/paraspatidar/bee27ef5e18209148d8d922d689b7327.js"></script></div>
 
All of them , internally make calls to fetch the current running server name & IP , and this is a security related call and thus due to this 3 lines of code , the application will break as the call is being restricted by Sandbox , as per <a href="https://github.com/projectkudu/kudu/wiki/Azure-Web-App-sandbox#local-address-requests">sandbox article</a> :
<table style="width: 739px;height: 139px" border="1" cellspacing="0" cellpadding="0">
<tbody>
<tr>
<td width="534" valign="top">Connection attempts to local addresses (e.g. <code>localhost</code>, <code>127.0.0.1</code>) and the machine's own IP will fail, except if another process in the same sandbox has created a listening socket on the destination port.
Rejected connection attempts, such as the following example which attempts to connect to <code>127.0.0.1:80</code>, from .NET will result in the following exception:</td>
</tr>
</tbody>
</table>
 
However in case you are using , On-Prem Database , then same piece of code will work as in case of Vnet , Sandbox treats differently to such calls and thus those calls doesn’t get banned in case of Vnet and works , as <a href="https://github.com/projectkudu/kudu/wiki/Azure-Web-App-sandbox#virtual-networks">mentioned here</a> :
 
<table style="width: 740px;height: 179px" border="1" cellspacing="0" cellpadding="0">
<tbody>
<tr>
<td width="623" valign="top">Azure Web Apps may set up their <a href="https://azure.microsoft.com/en-us/documentation/articles/virtual-networks-overview">virtual networks</a>, or VNets in order to facilitate connectivity between Azure and on-premise intranets. This special case of network connectivity is also handled differently in the sandbox. In particular, the aforementioned restrictions on private and local addresses are ignored if the target network interface belongs to the app. Other VNet adapters on the same machine cannot be accessed, and all other network limitations are still apply.
Additionally, the sandbox automatically affinitizes <a href="https://msdn.microsoft.com/en-us/library/windows/desktop/ms737625%28v=vs.85%29.aspx"><code>connect</code></a> and <a href="https://msdn.microsoft.com/en-us/library/windows/desktop/ms740149%28v=vs.85%29.aspx"><code>send</code></a> operations destined for VNet addresses to the correct VNet interface, in order to improve ease-of-use of the VNet feature.</td>
</tr>
</tbody>
</table>
 
Removing those 3 lines from code, will make your code running fine and you shall be able to create table or any such SMO operation.
So above are few most happening scenarios which you need to take care.]]></content:encoded>
</item>
<item>
<title>Using Azure Container Registry on Cross Subscription</title>
<link>https://docs.microsoft.com/archive/blogs/paraspatidar/using-azure-container-registry-on-cross-subscription</link>
<pubDate>Thu, 04 Jan 2018 08:49:40 GMT</pubDate>
<dc:creator><![CDATA[ParasPatidar]]></dc:creator>
<guid
isPermaLink="false">https://blogs.msdn.microsoft.com/paraspatidar/?p=897</guid>
<description><![CDATA[ 
In this article we we going to discuss one very common scenario of using an existing azure...]]></description>
<content:encoded><![CDATA[ 
In this article we we going to discuss one very common scenario of using an existing azure container registry across multiple subscription in Azure Account.
If you are new to azure container registry & azure web apps for containers , please refer my post here on step by step tutorial on how to setup 
<a target="_blank" href="https://blogs.msdn.microsoft.com/paraspatidar/continuous-deployment-with-web-app-for-containers-using-azure-container-registry-part-1/" rel="noopener">web app for containers using azure container registry</a>.
The Idea here to use the existing azure container is as follows :
<ol>
<li>Create Azure Container registry in one subscription.</li>
<li>Test if this is working fine by creating web app for container using this registry in same subscription.</li>
<li>If the test us Successful , then use this registry details as a private registry.</li>
<li>On Another Subscription , create a <a target="_blank" href="https://blogs.msdn.microsoft.com/paraspatidar/continuous-deployment-with-web-app-for-containers-using-azure-container-registry-part-1/" rel="noopener">web app for containers 
</a>
, but in Configure Container / docker
Container option , select the option for private registry and enter the details from point 3 with little correction (Image name should be in format <loginserverOfRegistory>/<Imagename>:<Image tag> ) which I will show you.</li>
</ol>
 
So based on details of my previous <a target="_blank" href="https://blogs.msdn.microsoft.com/paraspatidar/continuous-deployment-with-web-app-for-containers-using-azure-container-registry-part-4/" rel="noopener">post here
</a>and image shown below , here are registry details for point number 3 above:
Login Server : azureregistrycontainer.azurecr.io
Username : azureregistrycontainer
Password : Blurred Password
Server URL : <a href="https://azureregistrycontainer.azurecr.io" title="https://azureregistrycontainer.azurecr.io">https://azureregistrycontainer.azurecr.io
</a>
<a href="https://msdnshared.blob.core.windows.net/media/2018/01/image33.png">
<img width="708" height="547" title="image" class="shadow margineleft5" alt="image" src="https://msdnshared.blob.core.windows.net/media/2018/01/image_thumb33.png" border="0" />
</a>
 
Image name : samples1/php
Tag : latest
<a href="https://msdnshared.blob.core.windows.net/media/2018/01/image34.png">
<img width="731" height="599" title="image" class="shadow margineleft5" alt="image" src="https://msdnshared.blob.core.windows.net/media/2018/01/image_thumb34.png" border="0" />
</a>
 
Now , while creating web app on another subscription , please provide the details as mentioned :
<a href="https://msdnshared.blob.core.windows.net/media/2018/01/image35.png">
<img width="706" height="660" title="image" class="shadow margineleft5" alt="image" src="https://msdnshared.blob.core.windows.net/media/2018/01/image_thumb35.png" border="0" />
</a>
 
Or modify the similar details on Existing Web app for container in Docker Container Option:
<a href="https://msdnshared.blob.core.windows.net/media/2018/01/image36.png">
<img width="763" height="769" title="image" class="shadow margineleft5" alt="image" src="https://msdnshared.blob.core.windows.net/media/2018/01/image_thumb36.png" border="0" />
</a>
 
Please note , clicking on "Save” button here will take you back to Azure Container Registry setting, but that's just default UI functionality , ignore that.
 
<a href="https://msdnshared.blob.core.windows.net/media/2018/01/image37.png">
<img width="764" height="840" title="image" class="shadow margineleft5" alt="image" src="https://msdnshared.blob.core.windows.net/media/2018/01/image_thumb37.png" border="0" />
</a>
 
Now go ahead and try to browse your web app , it should be running fine same as that container image web app on original subscription.
Possible things to check if this doesn't work :
1. Check the resource explorer option for this web app and check config details , it should have entry as shown below :
<a href="https://msdnshared.blob.core.windows.net/media/2018/01/image38.png">
<img width="486" height="394" title="image" class="shadow margineleft5" alt="image" src="https://msdnshared.blob.core.windows.net/media/2018/01/image_thumb38.png" border="0" />
</a>
<a href="https://msdnshared.blob.core.windows.net/media/2018/01/image39.png">
</a><a href="https://msdnshared.blob.core.windows.net/media/2018/01/ResExplo.png"><img class="shadow margineleft5" src="https://msdnshared.blob.core.windows.net/media/2018/01/ResExplo.png" alt="" width="825" height="444" /></a><a href="https://msdnshared.blob.core.windows.net/media/2018/01/image39.png">
</a>
 
2. Verify that registry details and credentials as per step 3 are correct.
 
 ]]></content:encoded>
</item>
<item>
<title>Continuous deployment with Web App for Containers using Azure Container Registry – Part 6</title>
<link>https://docs.microsoft.com/archive/blogs/paraspatidar/continuous-deployment-with-web-app-for-containers-using-azure-container-registry-part-6</link>
<pubDate>Sat, 25 Nov 2017 18:24:00 GMT</pubDate>
<dc:creator><![CDATA[ParasPatidar]]></dc:creator>
<guid
isPermaLink="false">https://blogs.msdn.microsoft.com/paraspatidar/?p=745</guid>
<description><![CDATA[This Post is in continuation of Post :...]]></description>
<content:encoded><![CDATA[ This Post is in continuation of Post : <a href="https://blogs.msdn.microsoft.com/paraspatidar/continuous-deployment-with-web-app-for-containers-using-azure-container-registry-part-5/">https://blogs.msdn.microsoft.com/paraspatidar/continuous-deployment-with-web-app-for-containers-using-azure-container-registry-part-5/</a> and it is Part 6 of the thread.To start Over , please begin from <a href="https://blogs.msdn.microsoft.com/paraspatidar/continuous-deployment-with-web-app-for-containers-using-azure-container-registry-part-1/">Here</a>Our next steps are from Verifying Continuous Deployment  section .20. Go to Docker CLI.21. Modify the image or give the same tag mapping to any other image.     1) So now to do so , I will download the phpmyadmin container image from docker by running following command :               docker pull phpmyadmin/phpmyadmin               <a href="https://msdnshared.blob.core.windows.net/media/2017/11/clip_image021_thumb1.png"><img width="512" height="55" title="clip_image021_thumb1" style="margin: 0px;border: 0px currentcolor" alt="clip_image021_thumb1" src="https://msdnshared.blob.core.windows.net/media/2017/11/clip_image021_thumb1_thumb.png" border="0"></a>     2) Now if I verify the images in my docker by running command           docker images         it shows something like :          <a href="https://msdnshared.blob.core.windows.net/media/2017/11/17_thumb3.png"><img width="707" height="158" title="17_thumb3" style="margin: 0px;border: 0px currentcolor" alt="17_thumb3" src="https://msdnshared.blob.core.windows.net/media/2017/11/17_thumb3_thumb.png" border="0"></a>    watch carefully here:      Line 2 : the image NGINX is having tag as latest with image id 40960******       as I have mapped that image with Azure container registry end point sample1/php,       Line 1 : my sample1/php end point is having same tag and same image id as line 2.       This also gives us indication , that currently which image is mapped to our azure registry end point.   3) Line number 7 : Now my recently downloaded phpmyadmin/phpmyadmin image tag is also latest ,with image id f4674******         But that is not mapped with my existing azure end point ,        Thus in line number 9 , that end point with that image id is having Tag as <none>.   4) Now let me map the phpmyadmin image to azure end point by running following command :            docker tag phpmyadmin/phpmyadmin myregistry.azurecr.io/samples1/php       <a href="https://msdnshared.blob.core.windows.net/media/2017/11/clip_image025_thumb1.jpg"><img width="609" height="27" title="clip_image025_thumb1" style="margin: 0px;border: 0px currentcolor" alt="clip_image025_thumb1" src="https://msdnshared.blob.core.windows.net/media/2017/11/clip_image025_thumb1_thumb.jpg" border="0"></a>   5) Now verify the docker image again to see if it pointing to correct end point        <a href="https://msdnshared.blob.core.windows.net/media/2017/11/18_thumb2.png"><img width="733" height="170" title="18_thumb2" style="margin: 0px;border: 0px currentcolor" alt="18_thumb2" src="https://msdnshared.blob.core.windows.net/media/2017/11/18_thumb2_thumb.png" border="0"></a>  6) Look closely ,  7) Now line 1 NGINX local image having image id 4096*** with tag latest.  8) Line number 4 :This same image id 4096*** , the tag has become <none> , that means now NGINX is not pointing to azure end point samples1/php any more   9) Line number 5 : Phpmyadmin/phpmyadmin local one having image id f46764*** with tag latest ,  10) Line number 6 : Same image id is now pointing to azure container registry end point samples1/php with tag latest.  11) From above, we have mapped phpmyadmin/phpmyadmin image to azure container registry and pushing this on on registry will auto deploye phpmyadmin image on our web app , which is currently running nginx image. 22. Push the image to Azure Container Registry.     docker push myregistry.azurecr.io/samples1/php     Run following command will push this image on azure registory , which should ideally push it on Azure web app as well .       <a href="https://msdnshared.blob.core.windows.net/media/2017/11/clip_image029_thumb1.jpg"><img width="757" height="167" title="clip_image029_thumb1" style="margin: 0px;border: 0px currentcolor" alt="clip_image029_thumb1" src="https://msdnshared.blob.core.windows.net/media/2017/11/clip_image029_thumb1_thumb.jpg" border="0"></a>     Now , in few minutes it should auto deploy phpmyadmin container on my web app 23. Browse the web app to see that new image is up and running.    <a href="https://msdnshared.blob.core.windows.net/media/2017/11/clip_image031_thumb2.png"><img width="528" height="318" title="clip_image031_thumb2" style="margin: 0px;border: 0px currentcolor" alt="clip_image031_thumb2" src="https://msdnshared.blob.core.windows.net/media/2017/11/clip_image031_thumb2_thumb.png" border="0" hspace="12"></a>24. After some time, the auto deployment logs are visible in the Azure Container Registry’s Web hook’s Logs/events        <a href="https://msdnshared.blob.core.windows.net/media/2017/11/20_thumb3.png"><img width="781" height="418" title="20_thumb3" style="border: 0px currentcolor" alt="20_thumb3" src="https://msdnshared.blob.core.windows.net/media/2017/11/20_thumb3_thumb.png" border="0"></a>]]></content:encoded>
</item>
</channel>
</rss>

If you would like to create a banner that links to this page (i.e. this validation result), do the following:

Download the "valid RSS" banner.
Upload the image to your own server. (This step is important. Please do not link directly to the image on this server.)
Add this HTML to your page (change the image src attribute if necessary):

<a href="http://www.feedvalidator.org/check.cgi?url=https%3A//blogs.msdn.microsoft.com/paraspatidar/feed/"><img src="valid-rss-rogers.png" alt="[Valid RSS]" title="Validate my RSS feed" /></a>

If you would like to create a text link instead, here is the URL you can use:

http://www.feedvalidator.org/check.cgi?url=https%3A//blogs.msdn.microsoft.com/paraspatidar/feed/

Home · About · News · Docs · Terms