Archive
The reply address does not match the configured – Azure ADAL and Dynamics 365
I was building a standalone HTML page which retrieves the Account records from Dynamics 365 and show them in a table.
As a prerequisite, I registered the application in Azure Active Directory’s ‘App registrations’.
Also configured the Application details in my HTML page
var organizationURI = “https://{orgname}.crm.dynamics.com”; //The URL to connect to CRM (online)
var tenant = “{Azure Tenant Name}.onmicrosoft.com”; //The name of the Azure AD organization you use
var clientId = “{Application ID}”; //The ApplicationId you got when you registered the application
var pageUrl = “http://localhost”; //The URL of your HTML page in your development environment.
After all the configuration, I was getting below error during the authentication
The reply address “http://…..” does not match the reply address configured for the application.
Reason and Fix:
- There must be a ‘Return URL’ configured with your application URL (i.e., HTML url in my case).
- To configure the ‘Return URL’
- Connect to ‘Azure Active Directory’ –> App registrations
- Select your configured Application
- Under ‘Settings’, click on ‘Reply URLs’
- Add your application URL (i.e., HTML url in my case)
- Rerun the Application and you should be able to connect and get Accounts
Refer this MSDN article for step by step to connect via ADAL
🙂
Azure Deployment Slots – Deploy and Swap
Assume that you have your live application deployed on Azure running and you must deploy a hot fix.
The option you got is, you might want to take your application down for some time till your hot fix deployed.
How about you deploy the hot fix with no downtime, the answer is Azure “Deployment Slots”.
Create a Deployment Slot:
To use ‘Deployment Slots’, make sure you are running with Standard or Premium Azure Service Plan before adding a slot
- Connect to Azure subscription and open your existing ‘App Service’
- Under ‘DEPLOYMENT’ section, select ‘Deployment Slots’ and click on “Add Slot”
- In the next screen, provide Slot name and choose ‘Configuration Source’. I gave my Slot name ‘Staging’ and in the ‘Configuration Source’:
- If you choose your existing ‘App service’ all the settings including ‘Application Settings/Diagnostic Settings/…’ will be copied to this slot
- Or you can choose ‘Don’t clone configuration….’ Option, if you want your slot to be clean and no carry over settings.
- Click ‘Ok’
- After few seconds, you would get notification that your slot is ready
- Once slot setup completed, your main App name will come as prefix of your slot (Ex: If ABC is my web app; my Slot name is ABC-staging)
Publish Website to Slot:
- Use Visual studio “Publish Web” option
- Select “Microsoft Azure App Service” and choose your main “App Service” and “Deployment Slots -> {Slot}”
- Click “Publish”
- After publishing, your slot would work as any other Web App. You can give the slot URL to test to run BVT
Swap Slot:
- Once you feel your slot is fine and can be promoted as main App
- Click on ‘Swap’
- Select ‘Source’ and ‘Destination’
- Main Web App would always represent as “production”
- “Staging’ is the name of your slot
- Click Ok
- It would take couple of minutes to complete Swap
- Once Swap completes, end users who are accessing would start getting new build with virtually no down time.
Useful points:
- If any errors are identified in production after a slot swap, roll the slots back to their pre-swap states by swapping the same two slots immediately
- You can check your available ‘Deployment Slots’ by opening your Service Plans.
🙂
Azure Web Deploy – Time out errors
Recently when we were trying to publish a web site to Azure ‘Deployment Slot’ using Visual Studio “Web Deploy” option, we encountered either Time out exception or VS hung after few files push.
Reason for this exception could be due to the enormous transactions on main (Prod) web app of the ‘Deployment Slot’.
Work around:
- We found a work around by using Drag and Drop feature of Kudu service deploying to wwwroot folder directly.
Steps:
- Publish the web site to your machines local drive
- ZIP the files (***You must select all the files and Zip it; Don’t zip the folder)
- Open the Deployment Slot’s Kudu Service (Go to ‘Advanced Tools’ -> Go)
- On the Kudu page, navigate to Home -> site -> wwwroot
- Drag and drop the zipped folder of your published web site.
- Wait for the process to complete publish.
🙂
Access and Edit Web App files hosted in Azure
I have an Asp.Net Web application hosted as a Web App in my Azure instance.
One of the requirement I frequently get is to view or edit the published ‘Web App’ files from Azure Portal.
As we cannot access the ‘Web App’ files from Azure portal, one of the simpler way to access the files is by using the Visual Studio ‘Server Explorer’.
- From the Visual Studio, open the ‘Server Explorer’ window
- Connect to the Azure Subscription
- Select the Web App under ‘App Services’ node and access the files.
Pre-requisites:
- You need to have Azure SDK 2.7 installed.
- Visual studio 2013 or higher version.
🙂
‘Publish Web’ option not showing up existing Azure Web Apps – Visual Studio 2015
I am using VS 2015 to publish my web application to one of my Azure web apps.
But all sudden the “Publish Web” window was not listing the existing web apps.
Not listing existing web apps
Fix:
- Install latest Microsoft Azure SDK 2.9.6 for VS 2015 (Download)
- You can also use ‘Microsoft Web Platform Installer’ for installation.
Install azure SDK 2.9.6
- Open the VS 2015 and choose ‘Publish’ and you would get existing web apps listed.
Publish-web-new-azure-web-apps
🙂
‘The given share name\prefix is not a valid name’ error – Azure ‘New-AzureStorageShare’ command
Other day, while I was creating a shared location in Azure using Azure Power Shell cmdlets, I got below error
The given share name/prefix ” is not a valid name for a file share of Microsoft Azure File Service
share name/prefix is not a valid name
Reason:
- “New-AzureStorageShare” command accepts share name only in lower case.
Fix:
- Update the command $s = New-AzureStorageShare “telcoip” -Context $ctx
Refer this Create shared drive using azure article on steps to share a location in Azure.
🙂
Badges
