Webinar creation fails with "Could not find culture info for organizer locale" even though organizer's locale fields are all valid

Question

Webinar creation fails with "Could not find culture info for organizer locale" even though organizer's locale fields are all valid

Bård Harald 0

I'm creating Teams webinars through the Graph API (POST /solutions/virtualEvents/webinars, delegated auth, VirtualEvent.ReadWrite scope) and keep hitting this on the create call: Could not find culture info for organizer locale: *.

I've now confirmed, by reading the organizer's own profile via Graph at the exact moment of a failed attempt, that every locale-related field I can find is actually set correctly:

preferredLanguage: nb-NO
usageLocation: NO
mailboxSettings.language.locale: nb-NO (displayName: "Norwegian Bokmål (Norway)")

So the organizer isn't missing a locale setting anywhere I can see - the API just doesn't seem to be finding it. I've also ruled out a missing OAuth scope (confirmed present) and tried sending startDateTime/endDateTime with a proper Windows timezone name ("W. Europe Standard Time") instead of UTC, in case the culture lookup fell back to the timezone - same error either way.

The one pattern I have noticed: it sometimes succeeds right after a fresh interactive reconnect of the delegated OAuth connection, then fails again on the next attempt with nothing else changed.

A few request IDs from repeated occurrences, if that helps someone check server-side logs: [Moderator note: Personally Identifiable Information removed]

Is this a known issue, or is there some other field (maybe a tenant-level Teams/virtual events policy default?) that this lookup depends on beyond the organizer's own profile?

Ashlesha Pawar (Tata Consultancy Services Limited) 395 Reputation points Microsoft External Staff

2026-09-02T05:12:17.07+00:00

We were able to independently reproduce the reported issue using Microsoft Graph with delegated authentication. The webinar creation request is returning the same “Could not find culture info for organizer locale” error.

We have confirmed that this is not specific to the customer’s application/request implementation. We will raise this with the engineering team for further investigation and will update this thread once we have more information regarding the root cause and fix.

1 answer

Your answer

Ashlesha Pawar (Tata Consultancy Services Limited) 395 Reputation points Microsoft External Staff

2026-09-02T05:12:17.07+00:00

We were able to independently reproduce the reported issue using Microsoft Graph with delegated authentication. The webinar creation request is returning the same “Could not find culture info for organizer locale” error.

We have confirmed that this is not specific to the customer’s application/request implementation. We will raise this with the engineering team for further investigation and will update this thread once we have more information regarding the root cause and fix.

Answer 1

Hi Bård,

Thank you for sharing the details of your situation and for providing the request IDs.

Based on the information you provided, the organizer’s visible locale settings appear to be configured correctly, and the required delegated permission is already present.

Since webinar creation may succeed immediately after a fresh interactive OAuth connection but fail again on a subsequent attempt without any other changes, this may be related to how the delegated session, request headers, or organizer locale is being processed, rather than a permanently missing locale setting in the organizer’s profile.

As a final client-side check, please:

Capture or inspect the actual outbound request and confirm that it explicitly contains a valid header, such as: Accept-Language: nb-NO

You may also test with en-US for comparison. Please ensure that your connector, HTTP library, or middleware is not replacing the value with *.

If possible, send the same create request through Graph Explorer or Postman, using the same delegated organizer account and request body.

If the request succeeds consistently through Graph Explorer or Postman but continues to fail through your current integration, the behavior may be specific to the connector or its handling of the delegated session. If the same intermittent error occurs across different clients, this would further indicate that a server-side investigation may be required.

If the issue persists, it may stem from a deeper system-level cause. In this case, I recommend contacting your organization's IT administrator, who can submit a support request to Microsoft Support through the Microsoft 365 Admin Center. They’ll be able to access system-level information to investigate the issue thoroughly and provide assistance. At the very least, they can offer the most effective workaround to ensure your experience remains smooth and secure.

When submitting the support request, please include the request IDs and UTC timestamps, relevant tenant and organizer details, sanitized request and response data, and the results of your additional testing.

For detailed guidance on how to open a support ticket with Microsoft Support, please refer to: Get support - Microsoft 365 admin | Microsoft Learn
In case you do not know who is your IT admin, kindly refer to this article: How do I find my Microsoft 365 admin? - Microsoft Support

I hope this helps move the case forward. Should you have any further questions or need additional assistance, please feel free to reply in the comments below.

If the answer is helpful, please click 'Yes' and kindly upvote it.

Note: Please follow the steps in the forum documentation to enable e-mail notifications if you want to receive the related email notification for this thread.