microsoft / microsoft/PowerPlatformConnectors
[BUG] Create from Azure Service (Preview) | "Fix it in Azure" goes to deprecated classic Azure Functions management experience
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 1.3k
- Forks
- 1.5k
- Avg merge
- 5d 15h
- Merged PRs (30d)
- 11
Description
Type of Connector
Custom Connector
Name of Connector
Create from Azure Service (Preview)
Describe the bug
In Power Apps, when trying to implement Custom connectors, the Create from Azure Service (Preview) can throw the following error:
An app runtime version of ~1 and the API definition are needed before importing. [Fix it in Azure] | [Learn more]
The [Fix it in Azure] link will go to an error page with the message "The classic Azure Functions management experience is deprecated. Please use the new experience"
Is this a security bug?
No, this is not a security bug
What is the severity of this bug?
Severity 3 - Minor issue
To Reproduce
In Power Apps
Custom connectors (left-hand side blade menu)
New custom connector
Create from Azure Service (preview)
Azure service: Azure function
If not using Azure API Management, this throws the below error:
An app runtime version of ~1 and the API definition are needed before importing. [Fix it in Azure] | [Learn more]
Expected behavior
Link should take user to the appropriate place in Azure where they are able to define this definition within an Azure Function, crucially without using Azure API Management (as "Azure Function" was selected).
Environment summary
N/A
Additional context
N/A
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the flow through Power Apps → Custom connectors → New custom connector → Create from Azure Service (preview) → Azure function, then follow the reported “Fix it in Azure” link. Verify that the link reaches the current Azure Functions experience for defining the required API definition without Azure API Management; done means the deprecated classic management page is no longer opened.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure
- Domain
- cloud
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 32/100