Azure Integration Account Maps in Visual Studio - azure

I am using Azure Logic Apps. I have uploaded Map and Schema in Integration Account and assigned it to my Logic App project.
The issue is that I can see my schema and map in Logic App Designer view in azure portal, But not in my Visual Studio 2017 Logic App Designer.
Screenshots can be seen below.
Azure Portal:
Visual Studio:
I have to use Visual Studio, its in our requirements. I don't know why Visual Studio not getting Maps/Schema in the list.
Any help please?
Regards,

Open Logic App in Logic App Designer.
Press F4 to bring up the properties window
Select the Integration Account from the first drop down

Related

Import Logic app built in Azure Portal into Visual Studio with parameters

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.

Azure Logic App Integration Tools in Visual Studio 2017

I am an experienced BizTalk developer who is now moving on to Azure logic apps. I have installed Visual Studio 2017 and added the "Azure Logic Apps Tools for Visual Studio" through the Tools|Extensions and Updates menu. However, I don't see an option for creating/editing XML schemas(.xsd files), I don't see the BizTalk EDI X12 schemas and there is no option for creating a map. What am I missing? I have searched and searched with no luck. Thanks.
XSD & Maps are part of the Azure Integration Account service. You need the Microsoft Azure Logic Apps Enterprise Integration Tools in order to use those. You will see that the mapper is very similar to what you know from the BizTalk-world.
I'm not sure Microsoft Azure Logic Apps Enterprise Integration Tools is already supported in VS 2017. I know it's supported on VS 2015.
On a side note, xsd's and maps created using a BizTalk Server Project will also work fine in an Azure Integration Account and Logic Apps,but might lead to a more complex ALM-story.
Right now there is no tooling available for Visual Studio 2017, only for Visual Studio 2015.
The tools are based on the BizTalk components and those components are only available for Visual Studio 2015.
You can download EDI schemas from Open Source Github, but only EANCOM and EDIFACT, X12 messages have been removed due to licensing questions https://github.com/Microsoft/Integration/tree/master/BizTalk%20Server/Schema

Not able to see Add->Existing Project as Azure Web Job Option when I right click on Web project in Solution Explorer of Visual Studio 2017

When I right click on the Web Project in the Solution Explorer of Visual Studio 2017, I don't see an option 'Add Existing Project as Azure Web Job'.
I did install Nuget-packages such as Microsoft.Web.WebJobs.Publish for the web project.
I am following this link https://learn.microsoft.com/en-us/azure/app-service-web/websites-dotnet-deploy-webjobs#convertlink to enable automatic WebJobs deployment with a web project.
Ideally, I am supposed to see like this, but that highlighted option is not shown in my visual studio 2017
Click to see image for how actually visual studio should have shown me an option
I don't see an option 'Add Existing Project as Azure Web Job'.
As far as I know, Visual Studio does not support to deploy WebJobs with ASP.NET Core Web Application currently.
But this feature is available in ASP.NET Web Application.
If you can not see 'Add Existing Project as Azure Web Job' option in your ASP.NET Web Application, you can try to repair or reinstall your Visual Studio and upgrade/reinstall your Azure SDK.

Debug Azure Germany with different Account

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

Deploy Azure WebApp from Visual Studio Team Services (VSO)

I try to setup my deployment source in azure portal for a given web app.
When i navigate to Web App > Deployment Source > Choose Source > Visual Studio Team Services i am not able to choose my Visual Studio Team Services account.
after selecting Visual Studio Team Services a cannot choose any project. Believe me, there are projects...
There are two things that you need to make sure of for this to work:
your VSTS account needs to be backed by AAD
you need to link it in the Azure portal
For more detail on exactly what this means, see this wiki page.

Resources