Видео

What error are you getting? Working with InApp or Managed Connector in Logic App Standard or Consumption? Lots of variables to consider. One thing, make sure when working with the Service Bus you need to set permissions at the Namespace level, not at a queue level.

@@StephenWThomas i am working in standard logic app with built in connector for service bus and storage account. Yes, i have set the roles and permissions at namespace level only…

Thanks! The service bus is so powerful and I think I lot of people forget how simple it is to work with! Take care.

I do not think it works that way. In code, I would do a ToUpper to ToLower to ensure the case wasn't an issue. If you can, enforce the sender to always use Upper to Lower case. Otherwise, you might have to have two conditions.

Thanks, will do!

Well, unlike BizTalk, where this was easy for you it is a bit harder for Service Bus. If you want to filter and route data inside your message, you need to build a process to read the data. Either a Function or Logic App could do this to receive the message, read it, and route it to the correct queue. Or have some other type of pre-process like a web service. Even better, have the sender put the data needed into the message properties, but usually places do not want to change to do it. Hope this helps.

It's kind of an art vs a science. I would think the 2 core option would work perfect for that type of setup. It is more about the message volume & size and if you will have spikes in that load. At the end of the day, the only way to know for sure is to setup a dev environment and run some basic load tests. Once you get the sizing down, make sure you look at getting a reserved instance for 1 or 3 years. It'll save you around 30%. Also, if I read it right as of now Microsoft doesn't charge any fees if you do cancel early. Hope this helps.

Glad you enjoyed it

About a month ago I switched to Bing for search. Twice, I've gotten AI results that were totally wrong. I looked at the references, and it flat out said "This is not supported" yet the AI said, "Yes it is supported". That said, if I want a sample table, sample json message, sample text, or any sample code doing something specific, it's great! With AIS, a lot of the services are graphical with a UI. So I'm not sure how much help it'll add for now. For starters inside Logic Apps, I'd really love to be able to search for a connectors and have it be smart about it. I was trying to "Call A Logic App" - never found it because it's called "Call a workflow". Same issues with XML related connectors. What are your thoughts?

You might want to look at using Logic App Consumption - the costs are much lower to low volume / demo scenarios. For Logic App Standard, I think what you are looking for is just to run the standard edition inside Visual Studio Code. It's not very hard to set up, and it's getting easier. I have a video on it here www.stephenwthomas.com/azure-integration-thoughts/getting-started-with-logic-apps-standard/ It's almost a year old so I think things are more manageable now. Getting set up on a stand-alone server is more complex. I think you'd need ARC and a larger setup than you would want to deal with.

I'll see what I can do but it'll be a few months down the line.

Great feedback, going to be doing this going forward.

I was a paper plate but I think we have the same issue with a ceramic plate as well.