Azurre sdk java for logic app management api - 1.10.0 beta versiob[BUG]

[suvvi]

Describe the bug Getting below error while creating logic app with integration account name specified like below

"integrationAccount": { "id": "/subscriptions/xxxx/resourceGroups/rgxx/providers/Microsoft.Logic/integrationAccounts/namex, "name": "xx", "type": "Microsoft.Logic/integrationAccounts" }

Exception or Stack Trace The integration account id must be provided in the 'integrationAccount' property of the workflow

To Reproduce Steps to reproduce the behavior:

Code Snippet Add the code snippet that causes the issue.

Expected behavior A clear and concise description of what you expected to happen.

Screenshots If applicable, add screenshots to help explain your problem.

Setup (please complete the following information):

• OS: [e.g. iOS]
• IDE: [e.g. IntelliJ]
• Library/Libraries: [e.g. com.azure:azure-core:1.16.0 (groupId:artifactId:version)]
• Java version: [e.g. 8]
• App Server/Environment: [e.g. Tomcat, WildFly, Azure Function, Apache Spark, Databricks, IDE plugin or anything special]
• Frameworks: [e.g. Spring Boot, Micronaut, Quarkus, etc]

If you suspect a dependency version mismatch (e.g. you see NoClassDefFoundError, NoSuchMethodError or similar), please provide

• dependency tree (mvn dependency:tree -Dverbose)

Additional context Add any other context about the problem here.

Information Checklist Kindly make sure that you have added all the following information above and checkoff the required fields otherwise we will treat the issuer as an incomplete report

• [ ] Bug Description Added
• [ ] Repro Steps Added
• [ ] Setup information Added

[ghost]

Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @Azure/azure-logicapps-team.

Issue Details

---

**Describe the bug** Getting below error while creating logic app with integration account name specified like below "integrationAccount": { "id": "/subscriptions/xxxx/resourceGroups/rgxx/providers/Microsoft.Logic/integrationAccounts/namex, "name": "xx", "type": "Microsoft.Logic/integrationAccounts" } ***Exception or Stack Trace*** The integration account id must be provided in the 'integrationAccount' property of the workflow **To Reproduce** Steps to reproduce the behavior: ***Code Snippet*** Add the code snippet that causes the issue. **Expected behavior** A clear and concise description of what you expected to happen. **Screenshots** If applicable, add screenshots to help explain your problem. **Setup (please complete the following information):** - OS: [e.g. iOS] - IDE: [e.g. IntelliJ] - Library/Libraries: [e.g. com.azure:azure-core:1.16.0 (groupId:artifactId:version)] - Java version: [e.g. 8] - App Server/Environment: [e.g. Tomcat, WildFly, Azure Function, Apache Spark, Databricks, IDE plugin or anything special] - Frameworks: [e.g. Spring Boot, Micronaut, Quarkus, etc] If you suspect a dependency version mismatch (e.g. you see `NoClassDefFoundError`, `NoSuchMethodError` or similar), please provide - dependency tree (`mvn dependency:tree -Dverbose`) **Additional context** Add any other context about the problem here. **Information Checklist** Kindly make sure that you have added all the following information above and checkoff the required fields otherwise we will treat the issuer as an incomplete report - [ ] Bug Description Added - [ ] Repro Steps Added - [ ] Setup information Added

Author:	suvvi
Assignees:	-
Labels:	`question`, `Logic App`, `Service Attention`, `customer-reported`, `needs-triage`
Milestone:	-

[joshfree]

Related issues in other public repos https://github.com/Azure/azure-powershell/issues/5233 and https://github.com/Azure/azure-powershell/issues/8410

@lilyjma can you please help ensure the service team follows up? It looks like there hasn't been traction on the other open github issues, above. Thanks!

[github-actions[bot]]

Hi @suvvi, we deeply appreciate your input into this project. Regrettably, this issue has remained inactive for over 2 years, leading us to the decision to close it. We've implemented this policy to maintain the relevance of our issue queue and facilitate easier navigation for new contributors. If you still believe this topic requires attention, please feel free to create a new issue, referencing this one. Thank you for your understanding and ongoing support.