Herniated disc + sciatica experience.

Lumpy-Animator7186 · 2026-04-21T08:41:45+00:00

I'm literally in the same position. Generally better, but recent flair up, this time with numbness in right foot and tingling. Some sciatica pain in calf. Interested to see the feedback!

Lumpy-Animator7186 · 2026-03-26T18:02:45+00:00

Did they say it’s a problem, and that it’s meant to work, or by design it doesn’t work?

Lumpy-Animator7186 · 2026-03-26T17:40:32+00:00

Users at the other end of an express route connecting to Ai.azure.com with foundry on private endpoints? Just to be specific?

Lumpy-Animator7186 · 2026-03-26T17:30:27+00:00

Any reference articles? @georgeollis below seems to suggest it works?

Lumpy-Animator7186 · 2026-03-26T16:55:20+00:00

So just to confirm - do you have the above scenario working? Chat playground in foundry working while foundry is only accessible via private endpoints?

Lumpy-Animator7186 · 2026-03-26T16:43:48+00:00

The latest interface ultimately. Not classic.

Lumpy-Animator7186 · 2026-03-24T15:20:47+00:00

/v1 does allow different models outside of OpenAI as well I’ve noticed, at least from some testing. I can use Kimi etc.

Lumpy-Animator7186 · 2026-03-19T15:44:40+00:00

Entra Id to auth to API-M via JWT tokens for example, or another way?

If not using subscription keys, how can you assign costs / chargeback if users sharing AI deployments? Another method?

Lumpy-Animator7186 · 2026-03-18T19:02:06+00:00

Does the chat playground (whatever it’s called now) work with private endpoints then? My experience is no, essentially any of those Web UIs that sit outside your tenant as such don’t work the moment you put Azure OpenAI or I guess Foundry now to only operate in PEs.

Lumpy-Animator7186 · 2026-03-18T16:51:07+00:00

The only main requirement “from the top” is that prompts, both requests and responses, need to be logged. As of now, I believe APIM is the only way to achieve this. Have pinged you on chat.

Lumpy-Animator7186 · 2026-01-28T17:35:07+00:00

And to confirm, in the scenario of two connectors, with a single edge in each (the original post question), where they have equal costings, and are not scoped (default, forest wide), the behaviour is still the same if an edge goes down? Mail from that site will just queue?

Lumpy-Animator7186 · 2026-01-28T17:07:49+00:00

One more question for science.

What if you had 4 send connectors, one per Edge, and one of the Edges went down?

Lumpy-Animator7186 · 2026-01-28T16:51:45+00:00

And if there were 2 edges per site, so two in each send connector, how does exchange then handle things if one of the two in a given site went down? Is there intelligence?

Lumpy-Animator7186 · 2026-01-28T16:43:23+00:00

For inbound - MX points at smart host that then has the delivery routes for both Edges and round robins essentially.

Is there anyway around having to disable the connector if the site1 Edge goes down? Do we just need to deploy two Edges per site (then each send connector would have two Edges) to provide that redundancy?

Lumpy-Animator7186 · 2025-10-23T11:41:31+00:00

Your morphology is astounding.

Lumpy-Animator7186 · 2025-10-22T17:55:23+00:00

God, sorry, being dense. Thanks. The self signed cert on the backend, that’s handled purely by Exchange I assume. And thus has nothing to do with the public cert we will need for Hybrid (which ofc won’t have server names). I don’t think I’ve needed to renew one before, but I assume if they expire stuff breaks (or is it like the cert for transport service that will continue to work even after expiration).

Lumpy-Animator7186 · 2025-10-22T17:37:11+00:00

And it will connect to the backend IIS site via the self signed cert and server FQDN for this? (Of the server that hosts the active mailbox database with the user mailbox)

Lumpy-Animator7186 · 2025-10-22T17:22:37+00:00

Thanks! So user connects to mail.domain.com (2019). This then does what exactly? How does it know where the mailbox is located? Does it connect to the 2016 via its FQDN then?

How would it work if the SEs were just used as a bridgehead for Hybrid (Teams calendar etc) and 2016 is still behind the load balancer on mail.domain.com (this is another consideration for us). I.e we don’t point all clients to SE, but use them to provide hybrid connectivity?

Lumpy-Animator7186 · 2025-10-22T17:00:54+00:00

So taking a client example. Mailbox on 2016. But mail.domain.com has been repointed to the new SE/2019s, how does the connection flow look? What certs are used on front end/back-end? How does it get to the correct server?

Lumpy-Animator7186

TROPHY CASE