Kibana version:
9.2.3

Elasticsearch version:
9.2.3

Original install method (e.g. download page, yum, from source, etc.):
tested on ECK 3.2.0 and with docker-compose

Describe the bug:

The Mapping view of a newly created index shows an add field option.
Adding and saving a field results in a 403 Forbidden error when running on a basic license.

Browser network requests show that the index mapping update is never attempted. Instead, clicking Save mapping FIRST triggers a GET to /api/ml/saved_objects/sync?simulate=false, which fails with 403 Forbidden.

This request fails on a basic license presumably because ML APIs are not available, and the issue disappears once a trial license is activated. I see the actual mapping update ( PUT to /api/index_management/mapping/{index}) takes place if the first ML request succeeds.

This is not clear in the UI nor the documentation.

Is this ML request intentional and necessary when mapping a field of any type from this UI?

Steps to reproduce:

• Install Elasticsearch and Kibana with a basic license (no trial activated)
• Create a new empty index PUT test-index
• In Kibana, navigate to Stack Management > Index Management > test-index > Mappings
• Click “Add field”, define any field, and click “Save mapping”

Expected behavior:
The UI should not invoke ML related APIs when saving index mappings, or it should clearly indicate that this action requires an ML-enabled license.

Screenshots (if relevant):

Errors in browser console (if relevant):

kbn-ui-shared-deps-npm.dll.js:1  GET http://localhost:5609/api/ml/saved_objects/sync?simulate=false 403 (Forbidden)

Any additional context: