[Extensiblity]: Page 502 OAuth2ControlAddIn - Make OnPrem functions accessible for BC extensions

[tuan-nguyen-fenwick]

Describe the issue

We would like to propose removing the [Scope('OnPrem')] property from all functions on page 502 OAuth2ControlAddIn in the System Application.

The OAuth2ControlAddIn page serves as a reliable mechanism for retrieving OAuth2 authorization codes that is very useful for BC apps that integrate with external OAuth2 services.

Currently, the OnPrem scope restriction prevents this page from being used in BC apps targeting the SaaS environment. As a result, we are required to replicate or reimplement similar functionality.

Expected behavior

Please remove the [Scope('OnPrem')] property from all functions on page 502 OAuth2ControlAddIn to make the page available for use in SaaS apps.

Steps to reproduce

None.

Additional context

No response

I will provide a fix for a bug

• I will provide a fix for a bug

[JesperSchulz]

🤖 AI triage completed. Product group, please validate the triage report (Microsoft internal access only, use Ctrl+Click to open in new tab).

---

_{Was this triage helpful? React with 👍 or 👎 on this comment to provide feedback.}

[darjoo]

Hi @tuan-nguyen-fenwick, what are the scenarios behind this?

Is it not sufficient to call the public functions via the OAuth2.Codeunit.al which will then invoke and display the page, returning the AccessToken?