web
You’re offline. This is a read only version of the page.
close
Skip to main content

Announcements

No record found.

News and Announcements icon
Community site session details

Community site session details

Session Id :
Finance | Project Operations, Human Resources, ...
Suggested Answer

JIT writer access to UDE

(3) ShareShare
ReportReport
Posted on by 394
Hello experts,
 
From Visual Studio 2022, when I request the JIT access, the writer access option is not available, only the reader. However I can still access the writer level last week.
Do you have any idea?
 
Thanks,
Categories:
I have the same question (0)
  • André Arnaud de Calavon Profile Picture
    305,150 Super User 2026 Season 1 on at
    Hi LB developer,
     
    This is odd. Have you recently installed an update for the development tools? I have the writer option available.
    Have you tried to restart Visual Studio?
    Are you running Visual Studio in administration mode?
    Is the environment itself in admin mode? If so, disable the admin mode.
    Check if there is a plugin update for the development tools.
     
     
  • Suggested answer
    DAnny3211 Profile Picture
    11,421 Super User 2026 Season 1 on at

    Hi,

     

    This behavior usually occurs because writer-level JIT access has been disabled or restricted by environment settings or security policy. In recent platform updates, Microsoft tightened JIT controls to reduce risk, so the SQL User Role dropdown often defaults to Reader unless:

     

    • The environment is in maintenance mode and the user has the System Administrator role.

    • The JIT policy in LCS explicitly allows writer access for that environment.

    • The request is made from an environment owner account or an account with the required Azure AD role.


    •  
     

    What to check:

     

    1. Environment settings in LCS

      • Go to Environment details â–¸ Maintain â–¸ Enable JIT access and confirm that writer access is allowed. If the option is missing, your project policy may have removed it.

    2. User permissions

      • Ensure your account has the Environment administrator role in LCS and the System Administrator role in the Finance app.

    3. Advanced option

      • In some builds, you must check Advanced before the dropdown shows additional roles (Writer, Maintainer).

    4. Recent policy changes

      • If this worked last week, confirm whether your organization applied a security policy update or if the environment moved to a managed tier where writer JIT is no longer permitted.


    5.  
     

    If these checks confirm that writer access is restricted by policy, the only supported way to regain it is through LCS project settings or by requesting a temporary elevation from your environment admin.

     

    Could you verify if enabling the advanced option or checking LCS JIT settings resolves the issue?

     

    Thanks and best regards,

    Daniele

    Note: This response was prepared with support from Copilot to ensure clarity and completeness.

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Introducing the 2026 Season 1 community Super Users

Congratulations to our 2026 Super Stars!

Meet the Microsoft Dynamics 365 Contact Center Champions

We are thrilled to have these Champions in our Community!

Congratulations to the April Top 10 Community Leaders

These are the community rock stars!

Leaderboard > Finance | Project Operations, Human Resources, AX, GP, SL

#1
Giorgio Bonacorsi Profile Picture

Giorgio Bonacorsi 804

#2
André Arnaud de Calavon Profile Picture

André Arnaud de Cal... 639 Super User 2026 Season 1

#3
Subra Profile Picture

Subra 528

Last 30 days Overall leaderboard

Product updates

Dynamics 365 release plans