AI · MICROSOFT · SHARED KNOWLEDGE

AI, in your work.

Understand what’s changing.
Discover what you can do with it.

IN FOCUS / AI & industry

Directions EMEA 2026: preparing for Paris

Dates, registration and AI topics in the announced Paris agenda, with questions and examples for evaluating Business Central solutions.

Read the story 4 min

TRY IT IN NEXO

A useful answer starts before the question.

Choose a task. Compare two requests. Take away a prompt with context.

Open the prompt workshop Interactive example · Fictional data · No signup
FROM IDEA TO NEXT STEP

“Summarise this meeting.”

ContextGoalFormat

“Extract decisions, actions and what still needs confirming.”

The difference is in what you ask.

EXPLORE NEXO

The latest, with perspective.

32 articles

Topic: All

Finance in BC29: functional changes and tax limitations

Microsoft lists three enhancements in public preview: multiple excise duties per item, withholding on employee transactions and vendor-specific self-billing number series. Their application depends on the process and configuration.

Microsoft · Announcement: · Editorial review

Financial Overview dashboard with revenue, net profit, margin and asset indicators, plus charts showing profitability and customer and vendor balances.
Financial dashboard for Microsoft Dynamics 365 Business Central in Microsoft Power BI. Used with permission from Microsoft.

OpenAI policies: what to review if you offer a model gateway

OpenAI’s policies will require prior approval to give third parties direct access to its models from November 20, 2026. The text distinguishes this service from integrating models into an application.

OpenAI · Announcement: · Editorial review

Diagram of LiteLLM connecting a developer to A2A agents, MCP tools and language model APIs.
LiteLLM, an example of a model gateway. © 2023 Berri AI · MIT notice and license.
nNexo CommunityEditorial review · 2026-10-27

ANNOUNCEMENT & AVAILABILITY

Official sources checked on October 27, 2026. The update is published; the previous version remains in effect until the new policies take effect.

Broad access through consistent standards

The announcement and effective date

OpenAI announced on October 21 that routers and gateways providing direct access to its models will need prior review and approval. The measure forms part of its initiative to apply consistent safeguards across providers, as explained in its official announcement.

The Help Center note confirms that the changes take effect on November 20, 2026. The previous version applies until then. Existing agreements and other applicable terms continue to be relevant.

Which services the requirement covers

The model-access section of the Usage Policies requires prior authorization when an intermediary platform or another service enables third parties to access OpenAI models directly. It clarifies that integrating models to power an application’s features does not, by itself, trigger this requirement.

Nexo interpretation: describe what customers can do and who provides access before classifying a product by its commercial name. The following hypothetical examples help prepare that discussion; they are not OpenAI decisions about specific services.

Hypothetical designWhat to review
An application summarizes documents within a defined workflow.Document the feature and the experience delivered to the user.
An API lets other developers submit their own requests to multiple models.Describe the access offered and request the applicable review.
An internal gateway centralizes employee requests.Ask how the requirement applies to this architecture; do not assume an exemption because it is internal.

Responsibilities for access providers

In its announcement, OpenAI also assigns partners responsibilities to maintain safeguards consistent with its own, investigate potential violations and coordinate enforcement so that restrictions remain effective across services.

Separately, sections 2.2 and 3 of the Services Agreement provide for integrating the API into applications for end users and make customers responsible for activity under their accounts. They also prohibit buying, selling or transferring API keys with third parties.

What to prepare and what remains unspecified

The announcement, policies and Help Center note reviewed do not specify an application channel, response times or transition arrangements for existing gateways. How the requirement applies to an internal gateway also needs confirmation from the provider.

For technical and product preparation, Nexo suggests:

  • Prepare a diagram of users, credentials, models and access paths.
  • Document safeguards, owners and responses to potential misuse.
  • Request written clarification of the process, the status of an existing service and applicable conditions before committing to a launch.

Created with AI assistance and reviewed by Nexo Community. Practical proposals and editorial interpretation are distinguished from documented facts.

Read the source ↗

CONNECT THIS IDEA

A useful next step.

AI & industry · 4 minDesigning a multi-agent HR assistant: decisions before implementationAI & industry · 3 minReporting in BC29: controlling layouts and accessing the inbox through APIs

More articles appear as you continue scrolling.