Why Out-of-Box Features Suddenly seems broken in ServiceNow?

Many ServiceNow administrators have seen a familiar problem: an out-of-box (OOB) feature that worked perfectly for months suddenly stops functioning for certain users. Although nothing changed in the user’s roles or group membership, the platform starts throwing errors such as “Security constraints prevent access.”

This article explains why this happens, what the hidden triggers are, and how to systematically diagnose and resolve these issues using proven techniques.

---

1. OOB Does Not Mean Static — ServiceNow Changes Behind the Scenes

A common misconception is that OOB features remain stable if administrators don’t modify them. In reality, ServiceNow routinely releases:

• security patches

• platform updates

• ACL improvements

• UI page updates

• reference qualifier fixes

Any of these can inadvertently tighten access to an OOB feature.

Real example:

The “Show Schedule” calendar worked last month. After a platform security update, the ACL on the underlying cmn_schedule_calendar table began enforcing stricter group access. Users now see an access error.

---

2. Data-Level Permissions Matter More Than People Realize

Even if roles haven’t changed, the data they are trying to access may have changed.

In ServiceNow, record visibility is impacted by:

• Group ownership

• Reference qualifiers

• Domain separation

• Table ACLs

• Field ACLs

• Record ACL scripts

For example, if a schedule record is owned by a group the user can no longer see, the calendar widget will fail—even though the user technically has the right roles.

Common data-level causes:

• The schedule was reassigned to a different group

• The group was renamed or deactivated

• User’s group membership changed indirectly (via AD sync)

• Domain was changed (intentional or accidental)

---

3. Reference Qualifiers Can Suddenly Exclude the Record

Many OOB widgets rely on reference qualifiers or filter conditions.
If those qualifiers begin enforcing updated logic (due to a patch or dictionary change), the record previously visible may now be excluded.

Example:

javascript: gs.getUser().isMemberOf(current.group)

If the user is no longer a member, the calendar lookup silently fails.

---

4. Security Patches Tighten ACL Behavior

ServiceNow frequently enhances ACL evaluation logic for security hardening.

Before:
A permissive or faulty ACL script quietly allowed access.

After patch:
The script now enforces strict evaluation → user loses access.

This is one of the most common causes behind sudden OOB access failures.

---

5. UI Page or Script Includes May Have Role Requirements

Even if a table ACL allows access, the UI Page rendering the calendar or widget may have:

• a role restriction

• a new script

• a changed include

• a new dependency on a secured API

A small unnoticed update can break the entire page for certain users.

---

6. How to Diagnose the Issue Quickly

Step 1 — Impersonate the User

Try to open the same record or page.

Step 2 — Enable Debug Security

Navigate to:
System Diagnostics → Debug Security

Then reproduce the error.
This will show exactly which ACL is blocking access.

Step 3 — Inspect the Schedule or Data Record

Check:

• group field

• ownership

• domain

• active status

• visibility through reference selectors

Step 4 — Review Platform Update History

Check:

• System Logs → Update Sets

• Plugin activations

• Patch history

• Scripts updated recently

Step 5 — Test with an Admin

If even admin struggles to open certain pages, the issue is UI-page related—not ACL related.

---

7. Preventing Future OOB Access Breakages

• Regularly review ACL scripts after platform upgrades

• Use ATF to validate critical workflows after patching

• Avoid depending on ACL scripts that reference specific users/groups

• Maintain good documentation of group ownership for key business objects

• Monitor the update history of all “show schedule”, “calendar”, or other UI pages

---

Conclusion

OOB features in ServiceNow can break even without visible configuration changes. The interplay of ACLs, data-level permissions, group ownership, reference qualifiers, and platform patches makes access an evolving landscape.

The key is recognizing that “nothing changed” is rarely accurate — something did change, even if indirectly.
By following a systematic debugging approach and understanding how access is evaluated, admins can resolve issues quickly and prevent unnecessary escalations or panic incidents.

Read More

Ultimate Troubleshooting Guide: Fixing ServiceNow + OneDrive OAuth, Token, and Folder Path Issues

Ultimate Troubleshooting Guide: Fixing ServiceNow + OneDrive OAuth & Folder Path Issues

ServiceNow’s integration with Microsoft OneDrive often works flawlessly—until it doesn’t.
Admins frequently see issues like:

• Files uploaded into the wrong user’s OneDrive folder

• Tokens regenerating but not applying properly

• “OAuth access or refresh token not available”

• OneDrive Spoke actions failing silently

• No prompt for Microsoft login when clicking Get OAuth Token

This troubleshooting guide gives you precise workflows to identify and resolve root causes related to ServiceNow OneDrive integration..

1. Verify You Are Using the Right OAuth Profile

Go to:

System OAuth → Application Registry

Confirm that:

✔ Only one OneDrive OAuth application exists
✔ Its Client ID matches Azure App Registration
✔ Its Client Secret is valid
✔ Grant Type = Authorization Code (required for OneDrive Spoke)

If there are duplicate profiles → delete or deactivate the unused ones.

2. Confirm You Are Clicking “Get OAuth Token” Under the Correct Credential

Navigate to:

Connections & Credentials → Credentials → (Your OneDrive Spoke Credential)

Then:

✔ Ensure this credential uses the same OAuth profile
✔ Ensure your connection record uses this credential
✔ Click Get OAuth Token only after logging in with the correct Microsoft user

3. Verify Microsoft Session Identity (THE #1 FAILURE POINT)

Go to https://myaccount.microsoft.com and confirm:

✔ Who is currently logged in?
✔ Is Teams logged in?
✔ Is Outlook logged in?
✔ Is OneDrive sync client logged in?

Incorrect account = incorrect OAuth token.

4. Fix Token Ownership: Generate Token for the Right OneDrive Account

To issue the correct token:

1. Sign out from all Microsoft apps

2. Clear browser cookies + cache

3. Open a new incognito window

4. Sign in to Microsoft as the intended OneDrive service account

5. Log in to ServiceNow as the same account

6. Click Get OAuth Token

If it still uses the wrong account:
– Use a different browser
– Use a clean VM
– Use a private Windows profile
– Disable “Windows Account Manager” in Edge settings

5. Test OneDrive Spoke Connectivity

Test using:

OneDrive → List Drive Items

✔ If results come from the wrong drive → wrong token
✔ If unauthorized → wrong permissions
✔ If empty → token is correct but folder path is wrong

6. Validate Graph Permissions

Your Azure App Registration must include:

Delegated permissions:

• Files.ReadWrite.All

• Files.Read.All

• User.Read

• offline_access

And admin consent must be granted:

Azure portal → App Registration → API Permissions → Grant admin consent

If consent is missing, tokens will work but operations silently fail.

7. Confirm the OneDrive Service Account Actually Has OneDrive Enabled

Go to the Microsoft Admin Center:

✔ The account must have a valid OneDrive license
✔ It must have logged in to OneDrive at least once
✔ Storage must be provisioned

If not, OneDrive Spoke will fail with misleading errors.

8. Check Whether the Token Belongs to the Wrong User in ServiceNow

Find token owner:

sys_oauth_credential.do

Look at the field:

Authorized by User

If this shows Hoff, admin, or any user except your service account → wrong identity is issuing the token.

9. Verify the Document Path Logic in ServiceNow

For Document Services:

Navigate to:

Document Management → Connection Configuration → OneDrive Settings

Check:

✔ Default folder
✔ Path variable mapping
✔ Whether a user-specific folder is enforced
✔ Whether the integration uses SharePoint or personal OneDrive

10. Reset Token If Needed

If things are completely broken:

1. Remove OAuth tokens from sys_oauth_credential

2. Remove token from OneDrive Spoke credential

3. Restart token flow (following Step 4)

Summary Checklist

Issue	Likely Cause
Files going to wrong OneDrive user	Microsoft session mismatch
No Microsoft login prompt	SSO or cached session
OAuth token unavailable	Client secret mismatch / expired token
OneDrive Spoke failing	Missing Graph permissions
Token stored under wrong ServiceNow user	Wrong login identity during OAuth
Files uploading but not into correct path	Incorrect folder mapping

Read More

How to Generate the Correct OneDrive OAuth Token in ServiceNow

How to Correctly Generate the OneDrive OAuth Token in ServiceNow

If your ServiceNow instance keeps uploading files into the wrong OneDrive folder, it means the OAuth token was issued for the wrong Microsoft account.

Here is the exact procedure to generate a correct token for the right service account.

Prerequisites

• OneDrive service account

• Azure AD admin account (for App Registration)

• OneDrive OAuth profile configured in ServiceNow

• Valid Client ID and Client Secret

Why This Procedure Is Necessary

With SSO environments:

• VDI login automatically logs users into Microsoft

• Teams/Outlook auto-start with cached credentials

• Office apps silently authenticate

This means clicking Get OAuth Token will always use whatever Microsoft session is active—even if you logged into ServiceNow with a different account.

Step-by-Step Procedure

STEP 1 — Completely log out of all Microsoft sessions

You must remove all cached Microsoft identity data:

✔ Sign out of Teams
✔ Sign out of Outlook
✔ Stop OneDrive sync client
✔ Close Office apps
✔ Log out of Office.com
✔ Clear browser cookies
✔ Restart the browser
✔ Optionally reboot the VDI session

STEP 2 — Open a new Incognito window

Do NOT use a normal window.
Normal windows share cookies from the VDI.

STEP 3 — Sign in to Microsoft manually with the OneDrive account

In the incognito window:

• Go to https://login.microsoftonline.com

• Sign in as OneDrive service account

• Complete MFA if required

At this stage, Microsoft knows the identity that should receive the OAuth token.

STEP 4 — Log in to ServiceNow with the same service account

Still in the same incognito window:

• Log in to ServiceNow as OneDrive service account

• Do NOT use impersonation

STEP 5 — Navigate to the OneDrive OAuth profile

Go to:

System OAuth → Application Registry → Your OneDrive OAuth Profile

STEP 6 — Click “Get OAuth Token”

This time:

• Microsoft sees OneDrive service account as the active session

• Microsoft issues the OAuth token for OneDrive service account

• ServiceNow stores the token under the OneDrive service account user context

STEP 7 — Validate the Token

Run a simple OneDrive Spoke action:

OneDrive → Create Folder

The folder should appear under OneDrive service account’s OneDrive path.

What If It Still Shows the Wrong Account?

Then the VDI or OS-level Microsoft session is still active.
Use one of these options:

• Try a different browser

• Use an entirely different machine

• Use a private Windows account profile

• Disable Teams auto-login temporarily

• Use a clean VM with no corporate SSO session

Once the correct token is captured, normal usage will no longer rely on the end-user’s Microsoft session.

Summary

To ensure ServiceNow writes files into the correct OneDrive folder:

• The OneDrive service account must be the Microsoft identity when generating the OAuth token

• Logging in to ServiceNow as that service account ensures correct token storage

• Clearing cached Microsoft sessions is essential in SSO environments

Following these steps guarantees the OAuth token belongs to the correct storage account every time.

Read More

ServiceNow + OneDrive OAuth Tokens: Why Files Keep Uploading to the Wrong User’s Folder

Why ServiceNow Uploads Documents to the Wrong OneDrive Folder — And How to Fix It

Many ServiceNow teams experience a confusing issue:

“We clicked Get OAuth Token, but files upload to the wrong user’s OneDrive folder.”

This happens even when logged in as a different ServiceNow user or when impersonating.
The root cause is not in ServiceNow at all—it’s in Microsoft session handling.

Let’s explain.

1. OAuth Token Is Issued to the Active Microsoft Session

When you click Get OAuth Token in ServiceNow:

• ServiceNow triggers an OAuth flow

• Microsoft checks who is currently signed in

• Microsoft issues an OAuth token for that account

• ServiceNow stores that token under the user record

Therefore, ServiceNow is simply the redirect channel.
Microsoft chooses the identity.

2. VDI / SSO / Teams Auto-login Makes This Worse

Many enterprise users log into a VDI or laptop using SSO, causing Microsoft apps like:

• Teams

• Outlook

• Office.com

• OneDrive client

…to automatically authenticate using a personal or admin account.

This means:

• Even if you open an Incognito window

• Even if you log in to ServiceNow as a different user

• Even if you impersonate

Microsoft will still issue a token belonging to the cached session.

3. Why You Were Never Prompted for Microsoft Credentials

Because the browser already had a valid Microsoft authentication session via:

• PingOne (if used)

• Native Windows sign-in

• Office apps auto-login

• VDI identity provider

Microsoft never prompts again unless that session is cleared.

4. How to Generate a Token for the Correct OneDrive Account

You must ensure the Microsoft session belongs to the OneDrive service account.

Correct procedure:

1. Sign out from all Microsoft apps (Teams, Outlook, OneDrive sync client)

2. Clear browser cookies

3. Open a clean incognito window

4. Manually sign in to Microsoft using the OneDrive service account

5. Log in to ServiceNow using the same account (real login, not impersonation)

6. Click Get OAuth Token

Now the token will belong to the correct OneDrive account.

5. Why Impersonation Does Not Work

Impersonation changes only the ServiceNow identity.

It does not (and cannot) change:

• The Microsoft identity

• Browser sessions

• SSO sessions

• Office login state

Thus, impersonation cannot control where files get stored.

6. Summary

ServiceNow does not decide where OneDrive files go.
The Microsoft account active during OAuth does.

To fix file uploads going to the wrong folder:

• Ensure the correct Microsoft identity is active

• Use clean browser isolation

• Log in to ServiceNow with the OneDrive service account before generating the token

Once properly configured, all files will upload into the correct OneDrive or SharePoint folder.

Read More

Understanding ServiceNow + OneDrive Integration: Why Two Microsoft Accounts Are Required

Understanding Why ServiceNow Needs Two Microsoft Accounts for OneDrive Integration

Integrating ServiceNow with Microsoft OneDrive often confuses teams—especially when they realize two different Microsoft accounts are involved:

1. A Microsoft OneDrive account

2. A Microsoft Azure AD (Entra ID) account

Why are both required? Let’s break it down clearly.

1. OneDrive Account — The Storage Identity

The OneDrive account is the identity that actually owns the files.

This is the account whose folder you will ultimately see files uploaded into. When ServiceNow pushes a document to OneDrive, it goes to the personal or shared folder of the account whose OAuth token ServiceNow is holding.

This account represents where the documents live.

2. Azure AD Account — The Admin Identity for App Registration

The Azure AD administrative account is used only for configuring the integration.

This account:

• Creates the App Registration

• Generates the Client ID

• Creates/rotates the Client Secret

• Grants Microsoft Graph API permissions

• Approves admin consent

This account does not store documents and does not represent a user on the OneDrive side.
It only provides the OAuth infrastructure.

3. Why You Cannot Use Only One Account

Because Microsoft separates:

• Identity used for API permissions (Azure)

• Identity owning the files (OneDrive)

ServiceNow must interact with both:

Function	Requires	Why
OAuth authentication	Azure account	App Registration + permissions
File upload	OneDrive account	Determines where the file is stored

4. Most Common Confusion in Organizations

Many teams mistakenly think:

“We updated the client secret in ServiceNow, but OneDrive still uploads into the wrong user’s folder.”

This happens because:

• The Azure credentials control the application

• The Microsoft session of whoever clicks “Get OAuth Token” controls the OneDrive identity

5. Summary

To successfully integrate:

• Use the Azure AD admin account only for configuring the OAuth application.

• Use the OneDrive service account to generate the OAuth token that ServiceNow will use during runtime.

Both identities serve different purposes, and both are required for a functional and secure integration.

Read More

ServiceNow Integration Best Practices

ServiceNow Integration Best Practices: A Complete Guide for New Beginners

Integrations are at the heart of ServiceNow’s power. Whether you’re connecting to HR systems, monitoring tools, finance applications, or external APIs, reliable integrations ensure seamless data exchange and a consistent user experience.

If you're new to ServiceNow , mastering integration best practices early on will save you countless hours and help you build robust, secure, and scalable solutions.

This guide walks you through the essential best practices every ServiceNow developer, architect, or admin should know.

---

1. Authentication: Begin with Security First

Authentication is the gateway to every integration, and thus must be approached with utmost care.

Best Practices

• Use secure industry-standard methods: OAuth 2.0, Basic Auth (over HTTPS), or Mutual TLS.

• Store credentials in Credential records or Connection & Credential Aliases—never hardcode them in scripts.

• Use Scoped Applications to isolate and manage sensitive credentials.

• Periodically rotate passwords, keys, and tokens.

• When possible, store secrets externally using tools like HashiCorp Vault.

---

2. Error Handling: Build for Failure, Recover Gracefully

Integrations fail—it’s inevitable. What matters is how well you capture, handle, and recover from errors.

Best Practices

• Log failures using gs.error() or custom log tables.

• Add retry logic for temporary (transient) failures.

• Use IntegrationHub error handlers or structured Scripted REST API responses.

• Avoid exposing internal details or sensitive data in error responses.

• Standardize error codes and message formats to improve troubleshooting.

---

3. Approval & Governance: Build With Control

Integrations impact multiple applications and stakeholders.

Best Practices

• Ensure all new integrations are reviewed by the Architecture Team.

• Collaborate early with the Platform Team.

• Follow organizational guidelines on security, compliance, data governance, and legal.

• Use a formal intake checklist for new requests.

• Conduct periodic reviews of existing integrations to keep them healthy.

---

4. Security Requirements: Protect the Platform

Security is non-negotiable in modern integrations.

Best Practices

• Enforce HTTPS for all external communication.

• Apply RBAC (Role-Based Access Control) to safeguard exposed data.

• Sanitize incoming data to avoid injection attacks.

• Share sensitive data only when absolutely necessary.

• Restrict access with IP ACLs, rate limits, or an API Gateway.

• Continuously monitor for suspicious API activity.

---

5. Field Mapping & Data Contracts: Bring Clarity to Your Data

Every integration is a contract—both systems must understand the data being exchanged.

Best Practices

• Document all field mappings between systems.

• Maintain version-controlled documentation for:

  • Required fields

  • Expected formats

  • Transformation rules

• Use Transform Maps, Data Sources, or Flow Designer transforms where applicable.

• Use API versioning to support future enhancements without breaking existing consumers.

• Assign ownership for each data element.

---

6. Preserver List & Cloning: Avoid Integration Surprises

Cloning instances is routine, but it can disrupt integrations if not handled properly.

Best Practices

• Coordinate with the Platform Team on the preserver list—a list of records that should not change during clones (credentials, endpoints, keys, etc.).

• Store environment-specific data (URLs, tokens) in sys_properties.

• Prefer scoped-application-level properties for better isolation.

---

7. Performance Optimization: Build Integrations That Scale

Performance is key when dealing with high-volume or frequent integrations.

Best Practices

• Use asynchronous processing when possible (REST async=true, Events, Script Actions).

• Avoid excessive polling; batch data transfers when possible.

• Implement rate limiting to prevent overload.

• Use Queueable interfaces or IntegrationHub spokes for bulk or repetitive tasks.

• Avoid Business Rules on high-volume tables—opt for Flow Designer or Script Actions.

---

8. Storage Management: Keep Your Instance Clean

Integrations generate logs, payloads, and temporary data. Without discipline, storage can quickly spiral out of control.

Best Practices

• Avoid storing large payloads unless necessary.

• Apply retention policies to logs and staging tables.

• Archive or purge old integration data regularly.

• Log metadata (timestamps, size) instead of full payloads.

• Use compression for large transfers.

---

9. Transaction Timeouts: Avoid Long-Running Nightmares

Timeouts can break integrations if not managed proactively.

Best Practices

• Set explicit timeout values in REST/SOAP Message configs.

• Use Scheduled Jobs or Scripted REST to break long-running tasks into smaller parts.

• Implement exponential backoff for retries.

• Document timeout expectations with external partners.

• Consider a Circuit Breaker pattern for unstable services.

---

10. Monitoring & Alerting: Know What’s Happening Under the Hood

A successful integration is one you can monitor and trust.

Best Practices

• Use IntegrationHub Logs, ECC Queue, or custom logs for visibility.

• Create alerts for failures, anomalies, or performance degradation.

• Build dashboards with Performance Analytics for a real-time view.

• Establish SLAs/SLOs for mission-critical integrations.

• Use Event/Alert Management for routing urgent issues.

---

11. Testing & Load Simulation: Validate Before You Deploy

Testing integrations thoroughly can prevent costly failures in production.

Best Practices

• Use real-world data volumes for testing.

• Simulate peak loads to identify bottlenecks.

• Use mock APIs to avoid impacting partners.

• Automate tests with ATF where possible.

• Track test results as part of your CI/CD audit trail.

---

12. Environment Flow: Promote Code the Right Way

A structured environment flow prevents chaos.

Best Practices

• Develop in Dev → validate in Test → deploy to Prod.

• Never promote update sets from personal or sandbox instances.

• Use Application Repository or CI/CD pipelines for deployment.

• Store environment-specific variables in scoped sys_properties.

---

13. Use URLs Instead of IPs: Design for Flexibility

IP addresses change. URLs don’t.

Best Practices

• Always use DNS-based URLs.

• Use short TTL DNS records when using load balancers.

• Ensure DNS performance and reliability in your network path.

---

14. Documentation & Knowledge Sharing: Future-Proof Your Work

Good integrations are documented integrations.

Best Practices

• Store documentation in accessible repositories (Confluence, SharePoint).

• Include:

  • Sequence diagrams

  • Field mappings

  • Data flows

  • API contracts

  • Escalation paths

• Make documentation mandatory for go-live and handover to support teams.

---

15. Change Management: Prevent Avoidable Disruptions

Even a small integration change can ripple across multiple systems.

Best Practices

• All integration changes must go through CAB review.

• Provide rollback plans for deployments.

• Communicate changes with impacted teams well in advance.

---

16. Integration Lifecycle Management: Think Long-Term

Treat integrations as long-lived assets, not one-time projects.

Best Practices

• Track usage, ownership, and cost (API quotas, vendor fees).

• Audit integrations regularly for performance and compliance.

• Decommission obsolete integrations cleanly to reduce clutter and risk.

---

Final Thoughts

Integrations are critical to a successful ServiceNow ecosystem. When done right, they enhance automation, reduce manual work, and create a connected digital enterprise. As a beginner, focusing on these best practices will help you build integrations that are secure, scalable, maintainable, and future-proof.

Mastering these principles sets you apart not just as a ServiceNow developer—but as a trusted integration expert.

Read More

Can ChatGPT make anyone rich?

You might have heard that ChatGPT can make anyone rich. What do you think? Is it real?

But actually, it’s a myth that ChatGPT can make anyone rich.

Perhaps, what is true is that tools like ChatGPT can help people work faster, learn skills, brainstorm ideas, automate tasks, or improve decision-making. But that is very different from guaranteeing wealth.

Here’s the grounded version:

✅ What ChatGPT can do

• Help you learn high-value skills (coding, writing, marketing, analytics, etc.)

• Speed up research, drafting, planning, and ideation

• Assist with automation of repetitive work

• Provide education and guidance that can improve your earning potential

• Help you analyze business ideas and avoid mistakes

❌ What ChatGPT cannot do

• Guarantee income or wealth

• Predict markets or provide insider financial advice

• Replace skill, work, or judgment

• Provide magical “get rich quick” strategies

🔍 The real advantage

People who gain the most benefit tend to:

• Use AI as a tool, not a shortcut

• Combine it with existing expertise or effort

• Apply it to real problems or creative work

I get why it sounds discouraging at first — but being honest doesn’t mean killing people’s motivation. In fact, realistic expectations are what actually help people succeed, while hype and false promises usually set them up for disappointment.

Here’s a clearer way to frame it that won’t discourage anyone:

🌱 1. “AI won’t make you rich instantly — but it can make you more capable.”

That’s not discouraging; it’s empowering.
Instead of “AI = money,” the message becomes:
AI = leverage.
People love that idea because it feels achievable.

🚀 2. Honesty protects people from scams and false expectations.

Many influencers hype “AI money machines,” and a lot of people end up wasting time or money.
Being transparent actually helps people make smarter decisions.

💡 3. Motivation doesn’t come from fantasy — it comes from seeing real paths.

Instead of saying “AI will make you rich,” you can say:

“AI can help you work faster, learn skills, and build things that can lead to more income.”

That inspires people without misleading them.

🧭 4. People need direction, not illusions.

Most people aren’t discouraged by realism; they’re discouraged when they try something hyped and it fails.
Showing them practical, achievable ways AI can help them earn more is much more motivating.

In the end, AI isn’t a magic money button — but it is a powerful tool.

If people use it to learn, create, automate, and improve their work, it can absolutely open doors to new opportunities and higher income. The real value comes from combining AI with human effort, skills, and good decisions. That’s where success happens.

Read More

ServiceNow Certification exam/test centers in India

ServiceNow Certification Registration

Instead of earlier partnership with Kryterion (via Webassesssor) to offer testing options for the ServiceNow Certification exams, ServiceNow University exams are now delivered through Pearson VUE. From Nov 18th 2025, you can register, schedule, and take exams directly on the Pearson VUE platform. Most important point to note here is that you do not need to create a separate Pearson VUE account. You can access exams directly through your ServiceNow University (SNU) account. The system uses secure Single Sign-On (SSO), so Pearson VUE connects automatically and seamlessly with SNU.

As per the new process, all exam registrations and scheduling now take place on the Pearson VUE platform. Vouchers can no longer be claimed or redeemed on Webassessor (Kryterion), and no new exam registrations or scheduling are allowed there. Your certification records and exam history have been automatically transferred, so no action is required on your part. It means that ServiceNow exam takes can no longer schedule new exams on Webassessor through Kryterion.

Once registered, you will have 90 days to complete your exam before the registration expires. Exam refunds will not be issued, once registration expires. The exam content and questions remain the same; only the layout and delivery interface are provided through Pearson VUE. Your company entitlements and discounts remain the same. There is no change to your eligibility or benefits. 

Note: Pearson VUE is a global testing provider and the official platform for scheduling and delivering ServiceNow University certification exams. All exams are managed through Pearson VUE, providing an enhanced and streamlined experience. 

For detailed information on training and certifications, visit ServiceNow Training and Certification site or contact training@servicenow.com

Additionally, you can go through ServiceNow Article for exams with Pearson VUE and FAQs on the revised process.

In India, following testing centers are available to take ServiceNow certification test.


NSE.IT Limited_Hyderabad
403, 4th Floor, Moguls Court, 5-9-60, Basheerbagh
Hyderabad
Andhra Pradesh


Gyanvriksh Interactive Private Limited
3rd Floor, QZ Plaza, Kothaguda, Opp Haveli,
Hyderabad
Andhra Pradesh


NSE.IT Limited_Vijayawada
9-62-81/C, 1st Floor, Ganapathi Rao Road
Vijayawada
Andhra Pradesh


NSE.IT Limited_Visakhapatnam
Door No 404, 47/10/26
Visakhapatnam
Andhra Pradesh


NSE.IT Limited_Guwahati
Parnil Palace, 2nd Flr R.G. Baruah Rd
Guwahati
Assam


NSE.IT Limited_Patna
UFO Mall, 5th Floor, Anishabad Crossing
Patna
Bihar


NSE.IT Limited_Chandigarh
2nd Floor, SCO 366, Sec 32 D
Chandigarh


NSE.IT Limited_Delhi
2E/22, 3rd Floor, Jhandewalan Extension
Delhi


Sites Learning India Pvt Ltd
WZ-O-98, First Floor, New Mahavir Nagar, Outer Ring Road 26
New Delhi
Delhi


Koenig Solutions_New Delhi
Basement KLJ Complex-I, Plot No 70
New Delhi
Delhi


Koenig Solutions_Goa
3rd Floor, B/T1, Campal Trade Centre
Panaji
Goa


NSE.IT Limited_Ahmedabad
302, Sutaria Complex, 3rd Floor, Ellisbridge
Ahmedabad
Gujarat


NSE.IT Limited_Rajkot
Rajkot LC Office No 412 Alap - B, 4th Floor
Rajkot
Gujarat


Shree Education Services
FF Shree Complex
Vadodara
Gujarat



eEdusolutions
SCO 324-25 2nd floor, Sector 38-D
Chandigarh, U. T.
Haryana


Koenig Solutions_Shimla
7, Prospect Lodge, Behind YMCA, Lower Jakhu
Shimla
Himachal Pradesh


NSE.IT Limited_Ranchi
Jha Niwaas, 1st floor Diversion Road
Ranchi
Jharkhand


New Horizons India_Bangalore
N-101, North Block, Manipal Centre
Bangalore
Karnataka


iDomain Technologies
#65, 1st Floor, 2nd A Cross, KHB Colony, Koramangala
Bangalore
Karnataka


CloudThat Technologies India Pvt. Ltd
668/B-17th C Main, Kormangala 6th Block
Bangalore
Karnataka


Parkus Technologies Pvt Ltd_India
12 Dental College Main Road, Munekollal
Bangalore
Karnataka


Anmol Technologies PVT LTD
No. 7, 3rd Floor, Parvath Acrade, Service Road
Bangalore
Karnataka


NSE.IT Limited_Bangalore
Azeem Gold, 13, 2nd Floor, Mosque Road
Bangalore
Karnataka


DTecH IT Education
No. 1, 1st Cross, 1st Main
Bangalore
Karnataka


Global Knowledge Network India _ Bangalore
Royal Barter, 1st Floor, No.78/1, Residency Rd.
Bangalore
Karnataka


Koenig Solutions_Bangalore
#47, 3rd Floor, 4th Block, 100 ft Road
Bangalore
Karnataka


Kalvi Institute_Bangalore
BP Plaza 91/6, TC Palya Main Road
Bangalore
Karnataka


NSE.IT Limited_Cochin
39/4609, A-1 Sreekandath Road, Ravipuram
Cochin
Kerala


NSE.IT Limited_Thiruvananthapuram
TC 15/320, Ground Floor
Trivandrum
Kerala


NSE.IT Limited_Bhopal
2nd Flr, Plot #61, E-6 Arera Colony
Bhopal
Madhya Pradesh


Space Computer and Training Academy
E-46 Balwant Nagar
Gwalior
Madhya Pradesh


NSE.IT Limited_Indore
Office No: 303, 3rd Flr, The Mark, 20/A,
Indore
Madhya Pradesh


SEED Infotech Ltd_Andheri Mumbai
A Wing, 402, 4th Floor,Vertex Vikas, Opp. Station Road
Andheri (East) Mumbai
Maharashtra

Loyal Bytes Global IT Services, Andheri Mumbai

B202, Mathuria Apts, Next to Vishal Hall

49 Sir M. V. Road, Andheri East

Mumbai

Maharashtra 400069

SEED Infotech Ltd_Aundh
Vasundhara Space, 2nd Floor, S.no 167/168, New D.P. Road
Aundh, Pune
Maharashtra


NSE.IT Limited_Mumbai
Trade Globe, Ground Floor
Mumbai
Maharashtra


SEED Infotech Ltd_Navi Mumbai
Vashi Plaza, C-Wing, Room No. 459
Navi Mumbai
Maharashtra


SEED Infotech Ltd_Pune
Panchsheel, 42/16, Erandwane, Income Tax Office Lane
Pune
Maharashtra


Knowledge Mine_Pune
No 208, Suratwala Mark Plazzo, Near HP Petrol Pump
Pune
Maharashtra


NSE.IT Limited_Pune
4th Floor, C-Block, Vega Centre, Shankar Sheth Road
Pune
Maharashtra


Certview Technologies Pvt Ltd
Office No 132, Wing ‘B’,1st Floor
Pune
Maharashtra


NSE.IT Limited_Bhubaneshwar
Banaprasad, Plot No.1210, 1st Floor, Bomikhal,
Bhubaneshwar
Orissa


NSE.IT Limited_Jaipur
109-110, 1st Floor Tambi Tower, Sansar Chand Road
Jaipur
Rajasthan


Mazenet Solution P Ltd_Nungambakkam
Gee Gee Emerald, No:312, 2nd Floor, 2AB,
Chennai
Tamil Nadu


Mazenet Solution P Ltd_T Nagar
Roop Emerald, Level-2, New No.45
Chennai
Tamil Nadu


Blue Lotus Technologies Private Limited
Plot 194, 195 First Main Road, Nehru Nagar, Kottivakkam
Chennai
Tamil Nadu


NSE.IT Limited_Chennai
Ground Floor, 96-104 Nungambakkam High Road
Chennai
Tamil Nadu


Global Knowledge Network India _Chennai
Unit No 508, 5th Floor Raheja Towers
Chennai
Tamil Nadu


Kalvi Institute_Chennai
#33/34, Anjugam Nagar, 2nd Street, Jafferkhanpe
Chennai
Tamil Nadu


Mazenet Solution P Ltd_Gandhipuram
12E, 1st Floor, Padmalaya Towers
Coimbatore
Tamil Nadu


NSE.IT Limited_Coimbatore
No. 65 & 66, Arpee Center, 320 N., NSR Road
Coimbatore
Tamil Nadu


Kalvi Institute_Coimbatore
#1527 Avinashi Road, Vratharaja Mills
Coimbatore
Tamil Nadu


Kalvi Institute_Dindugal
No 91 1st Floor, Sona Towers
Dindugal
Tamil Nadu


Kalvi Institute_Erode
155, 1st & 3rd Floor, DV Complex, Neheru Street
Erode
Tamil Nadu


Kalvi Institute_Madurai
No. 134, First Main Road, K.K. Nagar
Madurai
Tamil Nadu


Mazenet Solution P Ltd_Salem
Santosh Towers, 2nd Floor, Brindavan Road
Salem
Tamil Nadu


Kalvi Instutue_Theni
No 116 Edamal Street
Theni
Tamil Nadu


NSE.IT Limited_Trichy
No 6/1, 2nd Flr, Thangam Towers, Karur Bye Pass Rd
Trichy
Tamil Nadu


Kalvi Institute_Trichy
#171A, 10th Cross Street, Pon Nagar,
Trichy
Tamil Nadu


IPCC_Hazratganj
Ground Floor, Skylark Building
Hazratganj, Lucknow
Uttar Pradesh


NSE.IT Limited_Lucknow
Office no. 401, 4th Floor, Block A
Lucknow
Uttar Pradesh


Koenig Solutions_Dehradun
Plot No. 22, IT Park, Shastradhara Road
Dehradun
Uttaranchal


Indexpo Corporation
Binary House, 2 Circus Market Place
Kolkata
West Bengal


NSE.IT Limited_Kolkata
54/1/A, Hazra Road, Nav-Jeevan Apartments
Kolkata
West Bengal

Read More