Problem with linked subscription in logic app designer
- Dominant language
- TypeScript
- Stars
- 111
- Forks
- 109
- Avg merge
- 1d 23h
- Merged PRs (30d)
- 20
Description
### Describe the Bug with repro steps
When first loading Logic App Designer in azure portal you are asked to sign in.
If you sign in a different subscription than the one you want to work with it is not possible to change it anymore and going forward all dynamic loading will be made toward the signed in subs instead of the one you wanted.
Even if you destroy the logic app and recreate a new one despite being logged in the target subscription, you will still have the logic app designer relying on the erroneous initially signed in subs.
### What type of Logic App Is this happening in?
Consumption (Portal)
### Which operating system are you using?
Windows
### Are you using new designer or old designer
New Designer
### Did you refer to the TSG before filing this issue? [https://aka.ms/lauxtsg]()
Yes
### Workflow JSON
*No response*
### Screenshots or Videos
![image]()
### Browser
chrome Version 128.0.6613.121
### Additional context
*No response*
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reproducing the issue in the Logic App Designer for a Consumption workflow in the Azure portal using the new designer, signing into the wrong subscription first. Done means the designer can switch to the intended subscription and dynamic loading continues to use that selection after recreating the Logic App.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure, react, typescript
- Domain
- cloud, frontend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100