Tagging @DanielRosenwasser as this will affect TypeScript. This will not impact F# as they have an EA layer here.

@minestarks @uniqueiniquity @jessetrinity

Looks like we may be good here? #28343 (comment)

Right. But you'll have to move back to the nice, sane, name once i make this change :) Jusst giving you a heads-up, and also letting you block this on our end if you need more time.

@CyrusNajmabadi works for me, though please try to ensure this gets inserted earlier than the very end of a release cycle so we can respond without dealing with process overhead 😄

@sharwell any concerns here before i merge?

@CyrusNajmabadi if anything is referencing the interface with the long name, you can't rename it prior to those features moving the external access

Is there currently an external access version of this? I can go ahead and move us if that's the case.

I'll check. If there isn't, i can add it.

Is there currently an external access version of this?

Each partner team would need their own copy of the external access version.

@sharwell @uniqueiniquity ExternalAccess API added in e77231b

@sharwell i have added teh bridge type back in. can you ptal.

Hello @CyrusNajmabadi!

Because this pull request has the auto-merge label, I will be glad to assist with helping to merge this pull request once all check-in policies pass.

p.s. you can customize the way I help with merging this pull request, such as holding this pull request until a specific person approves. Simply @mention me (@msftbot) and give me an instruction to get started! Learn more here.

@uniqueiniquity once this merges into master, can you move onto the TS EA layer? thanks!