I want to publish an Azure Function Project using the Visual Studio 2022 publish option, but the Create button is always disabled without any visible reason for it:
How can I further research on this, get any error message or so?
Multiple times, Even I too faced the similar issue and haven’t found any permanent solution to it where I’m having the latest Version of Azure Functions Core Tools (4.0.4915), VS 2022 17.4.4 Version, .NET 6 SDK & Runtime installed.
I found the Similar SO issue where many users faced this issue #67813149.
I also found one of the causes of above issue - i.e., If we do not have access to the Azure Subscription, then I observed this Create button is greyed or disabled in the Visual Studio Azure Functions Project > Publish > Create New Function App Window.
Also, Please check you have right RBAC Access to manage the resources in the Subscription such as Contributor role for the Azure Function App Management. Visit this MS Q&A #669276 for more information.
After Sign-out and Sign-in in Visual Studio, System Restart, I got this fixed and working good as of now, but this should not be the fix. If you are facing this issue frequently, mail to azcommunity#microsoft.com.
Related
I deployed an Azure Function 2 months ago.
My VS Code was running perfectly according to my needs. Now I had to make some changes to my deployed function. but upon opening it is showing nothing.
Even from sidebar Azure extension it is not loading exiting azure functions. I tried everything, signin-signout, reinstalling, restarting, but nothing is working out for me. If I try to make a new function it asks me to create a new source although our company subscription is arleady listing in sidebar.
Can someone please help me in this regard?
Screenshot is attached.
We have a lot of function apps deployed since many months and in recent days, but they are showing in the Visual Studio Code Azure Extension under Function App Resources.
Few Steps to retrieve the existing resources in the VS Code Azure Extension are:
Uninstall and Install the Extensions like Azure Account, Azure Functions, Azure Resources, Azure Tools under Extensions blade:
Click on Settings (Gear Icon) > Make Sure your Microsoft Account is synced. If not, Sync it:
Check one of the workaround given for similar issue by #HAL9000
I want to import Logic Apps made in Azure portal imported in Visual Studio Project for Logic Apps.
I can download Logic App via Cloud Explorer & import from using this article https://learn.microsoft.com/en-us/azure/logic-apps/manage-logic-apps-with-visual-studio.
But after adding that visual studio to run or deploy I need to create parameter file manually. Is there some way to download existing Logic Apps with parameters so that when imported in Visual Studio that can be ready for run when committed in source control after downloading & adding to Visual Studio.
I have seen request for this feature in Azure supported by 211 votes but yet to be picked.
https://feedback.azure.com/forums/287593-logic-apps/suggestions/31833445-allow-to-export-logic-app-with-parameters-to-be-se
I am looking if anyone found some way to do this...
As the link you provided, it seems that the feature of exporting logic app with parameter directly does not exist now. You could vote up it to promote the implementation of the function.
For more details, you could refer to this article.
We recently changed our existing Azure subscription to Azure Germany and got a new account like name#company.onmicrosoft.de. Afaik this kind of domain is also used for Ofice365 accounts. Now i tried to add this account to my Visual Studio (2015 Community Edition), but i get this error (translated from german):
The account "" could not be added. Object reference not set to an object instance.
On the classic US Azure subscription we worked with our regular domain-Logins (name#company.de). Does anybody know how to connect to my new azure subscription, so that i can browse and debug? Thanks in advance!
Answer
As far as I know, it is not possible to add Azure Germany accounts to Visual Studio. But there are some workarounds for common tasks you do with Visual Studio.
According to Microsoft Technical Evangelist Malte Lantin, there seems to be something hardcoded in Visual Studio, that prevents VS from connecting to Azure Germany.
Workarounds
Deploy a solution
Download the publishing profile in Azure Portal and use it to deploy your solution
View SQL Databases
Navigate to the Azure Portal and click, view in Visual Studio
How to fix this bug?
Open Cloud Explorer (logged in)
Open "Files" folder for some Azure Web App (former Azure Website)
Result:
Cloud Explorer has encountered an unexpected error: Unable to retrieve
child resources.
Details: 'Newtonsoft.Json.Linq.JObject' does not contain a definition
for 'requestNamespace'
I'm using:
Microsoft Visual Studio Community 2015 Version 14.0.25431.01 Update 3
Azure App Service Tools v2.9.6 14.0.21111.0
Common Azure Tools 1.8
Microsoft Azure Tools for Microsoft Visual Studio 2015 - v2.9.41104.6
I had this problem and it was a permissions issue, mine was with a Cosmos Document DB database node.
I had my DevOps guy add me as a contributor to the IAM Azure role and it started working for me. So check all the permissions, and it is the cloud so sometimes you have to give it time to propagate the changes too.
I had this issue when both Azure Storage Emulator and Azure Storage Explorer trying to run at the same time. Try uninstall one or run only one at a time to solve the issue.
Have a look at troubleshooting guide might also help.
I'm having a pretty strange issue with Azure tools for VS 2013 (version 2.6). Whenever I try to sign in to my Azure subscription (e.g. from Server explorer or creating a new web role project) I get the following error:
Server Explorer
An error occurred during the sign in process: User 'foo#gmail.com' returned by service does not match user 'bar#outlook.com' in the request
OK
My subscription owned by 'bar#outlook.com' and I can perfectly fine sign in either to management portal in a browser (IE, Spartan and Chrome) - as well as in the Power Shell. Tried everything - cleaning up browser caches/cookies, resetting IE settings, playing with different IE security settings - nothign works.
Any help is appreciated - this issue drives me crazy.
P.S. I'm on Windows 10...
I had the same problem. Imported the certificate manually and everything worked ok: https://social.technet.microsoft.com/Forums/en-US/9cdafeb4-f459-436d-b2b8-9bc5c01f0df1/azure-tools-for-vs-cant-sign-in-to-subscription?forum=windowsazuredevelopment
I had this issue, to resolve it I:
Added 'foo#gmail.com' as an alias in my 'bar#outlook.com' Microsoft account, via account.live.com
Made the 'foo#gmail.com' email address the primary alias for my Microsoft account
I could then log in successfully in to Azure by pressing the Connect to Microsoft Azure button in the toolbar of the Server Explorer in Visual Studio 2013 and see all of my websites under the App Service node.
(When I'd used the certificate method described in the other post and Microsoft documentation I'd been able to see all my sql databases etc. but not the websites.)
Once I'd done all that I then switched my primary alias back to 'bar#outlook.com' and server explorer carried on working.
NB: If you're experimenting with this beware that there is a limit on how many times you can switch your primary.. as I have just discovered.. and now my primary is stuck on the wrong email address for a week.
NB2: If your connecting in order to be able to remote debug the website, then this can still be done by going to Visual Studio>Main Menu>Debug>Attach To Process, and then enter the URL of the site (without the http bit, e.g. mysite.azurewebsites.net) as the Qualifier and then attach to the w3wp.exe process.
I am having the exact same issue. It seems that the Azure sign-in in Visual Studio is redirecting to our organizational Single Sign-On instead of the Microsoft one. I have managed to work around this problem by using a Microsoft account that is not tied to my organization:
Create new Microsoft account or use an existing account not associated with your organization
In https://manage.windowsazure.com select Subscriptions/Manage Administrators
Choose Add+ and add the new Microsoft account as administrator to your subscription
Log on to Azure using the new account from Visual Studio
/Morten
I changed my Microsoft account's email address and had this problem. Adding an alias did not help.
The problem is to do with the Azure Active Directory Library for DotNet. For whatever dumb reason, they throw an exception when Azure returns an ID different than the one requested (if the server isn't crying about it, why make up an error and make the client deal with it?).
Since Azures's support was no help, I had to build a custom copy of the ADAL with that moronic exception removed and an assembly version matching the one used in VS2013 (2.11). Also importantly, disable strong name verification for the custom assembly.