Jentic OSThe workplace. An in-house AI platform for every employeeJentic OneSafe access. Agents reach your systems without holding keysJentic AIRThe foundation. Gets your existing platforms ready for AI
Pricing

GET STARTED

API DirectoryBrowse 10,000+ APIs ready for AI agent integrationDocumentationGuides and API reference

TOOLS

API ScoringCheck your AI readiness using our scorecardArazzo UIVisualize Arazzo workflows as interactive documentationArazzo EditorBuild and edit multi-step API workflows visually

COMMUNITY

GitHubOpen source projects and examplesOpen StandardsBuilt on open specs. Never locked in.
All ResourcesEverything in one placeBlogLatest articles and insightsTech Talk NewsletterAPIs, AI agents, architecture and strategyWebinarsLive sessions and on-demand recordingsReports & WhitepapersOriginal research on enterprise AI
About UsOur mission and teamCareersJoin our teamContactGet in touch
Try it now
Jentic OSJentic OneJentic AIR
Pricing
API DirectoryDocumentationAPI ScoringArazzo UIArazzo EditorGitHubOpen Standards
All ResourcesBlogTech Talk NewsletterWebinarsReports & Whitepapers
About UsCareersContact
Try it now
JenticJentic
Products
  • Jentic OS
  • Jentic One
  • Jentic AIR
For Developers
  • API Directory
  • Documentation
  • GitHub
Company
  • About Jentic
  • Careers
  • Contact Us
  • Trust Centre
ISO/IEC 27001:2022 certification badge issued by Prescient SecurityISO/IEC 27001:2022 certification badge issued by Prescient Security

Information Security Management System

Certified to ISO/IEC 27001:2022 by Prescient Security

AICPA SOC for Service Organizations logoAICPA SOC for Service Organizations logo

SOC 2® Type 1 report

Audited by Prescient Assurance

Terms & Conditions•Privacy Policy•
© 2026 Jentic Technology Ltd. All rights reserved.
2 Grattan Court East, Dublin, D02 VX86, Ireland
Switch to light modeSwitch to dark mode
APIs / Storage / Azure / Microsoft Storage Sync
Microsoft Storage Sync logo

Microsoft Azure Microsoft Storage Sync

Browse all Azure APIs
38
AI ReadinessNon-Ready (F)38/100
See full scorecard
Agent-ready OpenAPI document · curated by JenticStorageObject Storageoauth237 EndpointsREST

Know of an official OpenAPI document? Contribute it →

For Agents

Provision Azure File Sync services, register on-premises servers, and create sync groups that mirror file shares between Windows file servers and Azure storage. Covers 37 management endpoints across storage sync services, registered servers, sync groups, and cloud and server endpoints.

Use for: I need to create a new Azure Storage Sync Service in a resource group, Register a Windows file server with an existing Storage Sync Service, List all sync groups associated with a Storage Sync Service, Set up a cloud endpoint that points a sync group at an Azure file share

Not supported: Does not handle data plane file uploads, blob storage, or general-purpose Azure storage account creation - use for Azure File Sync control plane operations only.

Jentic publishes the only available OpenAPI specification for Microsoft Storage Sync, keeping it validated and agent-ready. The Microsoft Storage Sync API manages Azure File Sync deployments that centralize on-premises file shares in Azure while keeping the flexibility, performance, and compatibility of a local file server. It exposes operations to provision Storage Sync Services, enroll registered servers, define sync groups, configure cloud endpoints to Azure file shares, and add server endpoints that pair on-prem volumes with the cloud. Workflow operations allow agents to track long-running provisioning and synchronization tasks across regions.

Jentic One on GithubView OpenAPI Document

Install Jentic One Beta

Connect the Microsoft Storage Sync to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Microsoft Storage Sync, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

1

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fazure.com%2Fmicrosoft-storage-sync" | sh
2

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fazure.com%2Fmicrosoft-storage-sync" | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with Microsoft Storage Sync API.

Create and update Storage Sync Service resources scoped to an Azure resource group

Register on-premises Windows file servers and rotate their server certificates

Define sync groups that pair an Azure file share with one or more server endpoints

Configure cloud endpoints that connect a sync group to a specific Azure file share

Provision server endpoints with cloud tiering policies and free-space thresholds

Track long-running workflow operations for sync group and endpoint provisioning

Check the availability of Storage Sync Service names within an Azure region

Use Cases

Patterns agents use Microsoft Storage Sync API for, with concrete tasks.

★ Hybrid file server consolidation

Centralize branch office and headquarters file shares in Azure while keeping local read and write performance. The Microsoft Storage Sync API lets operators create a Storage Sync Service, register each on-premises file server, and pair on-prem volumes with Azure file shares through sync groups. Cloud tiering keeps frequently accessed files on local storage and offloads cold data to Azure, reducing on-prem capacity needs by 80 percent or more.

Create a Storage Sync Service named contoso-sync in resource group prod-files, register server srv-fs01, and create a sync group named legal-docs with a cloud endpoint pointing at the legal Azure file share.

Disaster recovery for on-premises file shares

Protect critical on-premises file shares by continuously syncing them to a geo-redundant Azure storage account. Operations teams use the Storage Sync API to add server endpoints to existing sync groups, monitor workflow status, and validate that all files have replicated to the cloud endpoint before declaring DR readiness. Recovery point objectives can drop from days to minutes.

Add a server endpoint mapping D:\shares\finance on srv-fs02 to the finance-sync sync group with cloud tiering disabled and confirm the provisioning workflow has completed successfully.

Capacity-aware cloud tiering policies

Reduce local storage spend on Windows file servers by configuring cloud tiering thresholds per server endpoint. Through the Storage Sync API, agents can patch existing server endpoint resources to adjust the volume free-space percentage that triggers tiering, monitor the resulting tiering activity through workflow operations, and roll out updated policies across many servers in a single batch.

Patch every server endpoint under sync group archive-data to set volumeFreeSpacePercent to 20 and report which workflows completed within five minutes.

Agent-driven Azure File Sync operations

AI agents can use Jentic to discover Microsoft Storage Sync operations by intent, load the structured input schema, and execute calls against management.azure.com without browsing Azure Resource Manager docs. Agents handle routine tasks like registering a server, recutting an expiring server certificate, or expanding a sync group to a new branch office without operator intervention.

Search Jentic for create a storage sync service, load the input schema, and execute it for resource group ops-sync in westeurope with the SKU StandardLRS.

Key Endpoints

37 endpoints — jentic publishes the only available openapi specification for microsoft storage sync, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

PUT

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.StorageSync/storageSyncServices/{storageSyncServiceName}

Create or update a Storage Sync Service

GET

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.StorageSync/storageSyncServices

List Storage Sync Services in a resource group

PUT

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.StorageSync/storageSyncServices/{storageSyncServiceName}/registeredServers/{serverId}

Register a server with a Storage Sync Service

GET

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.StorageSync/storageSyncServices/{storageSyncServiceName}/registeredServers

List registered servers under a Storage Sync Service

POST

/subscriptions/{subscriptionId}/providers/Microsoft.StorageSync/locations/{locationName}/checkNameAvailability

Check Storage Sync Service name availability in a region

PUT

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.StorageSync/storageSyncServices/{storageSyncServiceName}

Create or update a Storage Sync Service

GET

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.StorageSync/storageSyncServices

List Storage Sync Services in a resource group

PUT

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.StorageSync/storageSyncServices/{storageSyncServiceName}/registeredServers/{serverId}

Register a server with a Storage Sync Service

GET

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.StorageSync/storageSyncServices/{storageSyncServiceName}/registeredServers

List registered servers under a Storage Sync Service

POST

/subscriptions/{subscriptionId}/providers/Microsoft.StorageSync/locations/{locationName}/checkNameAvailability

Check Storage Sync Service name availability in a region

Jentic AI Readiness Score

This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.

M

Microsoft Storage Sync

- Non-Ready (F)
38/100
56
Foundational Compliance
62
Developer Experience & Jentic Compatibility
17
AI-Readiness & Agent Experience
94
Agent Usability
35
Security
100
AI Discoverability
Powered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.0
Show dimension breakdown
56

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: CSignals: 4
73%

Lint Results

Aggregated quality score from linter diagnostics, weighted by severity.

100%

Resolution Completeness

Percentage of `$ref` references that resolve successfully.

0%

Specification Validity

Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).

50%

Structural Integrity

Structural correctness score based on schema issues using logarithmic dampening.

62

Developer Experience & Jentic Compatibility

Clarity, completeness, and ingestion readiness for developers and tooling.

Grade: B-Signals: 4
0%

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

49%

Response Coverage

Percentage of operations with complete response definitions (success, client error, server error).

100%

Tooling Readiness

Health of API ingestion, bundling, and resolution within Jentic pipelines.

17

AI-Readiness & Agent Experience

Semantic breadth, depth, and agent comprehension for AI systems.

Grade: FSignals: 4
67%

Description Coverage

Coverage of descriptions across API elements.

0%

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

0%

OperationId Quality

Coverage, uniqueness, and casing consistency of operationIds for AI inference.

0%

Summary Coverage

Coverage of summaries across operations/tags/info.

94

Agent Usability

Functional utility, complexity comfort, and AI orchestration readiness.

Grade: A+Signals: 1
94%

Complexity Comfort

Agent comfort level based on API operational and structural complexity.

35

Security

Trust, risk posture, and security compliance.

Grade: FSignals: 1
35%

Authentication Strength

Average quality of security schemes based on authentication method strength (weakest link for OAuth2).

100

AI Discoverability

Findability, semantic richness, and reasoning readiness.

Grade: A+Signals: 1
100%

Descriptive Richness

Clarity and depth of descriptions across API elements.

View full reportHow the score is calculatedMore about the dimensions

Score it yourself

Every API in the directory is allowlisted, so you can re-score it with no key required.

Score your own APIScoring CLI agent skill
npx @jentic/api-scorecard-cli score <openapi-url>

Why Jentic?

What agents get from Jentic-routed access to this vendor.

Setup

Wiring Microsoft Storage Sync by hand means implementing Azure AD OAuth 2.0, minting an ARM-scoped bearer token for management.azure.com, handling the server certificate registration flow, and polling long-running workflow operations for sync group and endpoint provisioning yourself. Through Jentic you install once, import Microsoft Storage Sync from the API Directory, store the Azure AD credential once, and your agent calls it.

Permission scoping

The API puts the subscription, resource group, Storage Sync Service name, and server id in the URL path, so a rule can pin your agent to one Storage Sync Service: it can register servers and create sync groups under that service and nothing else. You choose the operations it may call, so destructive ones like deleting a registered server or a sync group are not included unless you add them.

Credential isolation

Your Azure AD credential is stored once, encrypted, by your own Jentic One instance and exchanged for a short-lived ARM-scoped bearer token at execution time. It never enters the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'create an Azure storage sync service' or 'register a file server with Azure File Sync', and Jentic returns the matching ARM operation with its input schema so the agent supplies the resource group and SKU and executes.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Complementary

Azure Storage Management

→

Manages the Azure storage accounts and file shares that Storage Sync replicates to.

Choose this when the agent needs to create or configure the underlying storage account or file share before pointing a Storage Sync cloud endpoint at it.

Complementary

Azure Resource Management

→

Manages the resource groups and tags that contain Storage Sync Services.

Use this when the agent needs to create the resource group or apply tags before deploying a Storage Sync Service.

Alternative

Azure Recovery Services Backup

→

Backs up file shares and on-premises servers without continuous sync semantics.

Choose this when the user wants point-in-time backup and restore of file data rather than continuous synchronization with cloud tiering.

FAQs

Specific to using Microsoft Storage Sync API through Jentic.

Why is there no official OpenAPI spec for Microsoft Storage Sync?

Microsoft Azure does not publish an OpenAPI specification for the Storage Sync Service Resource Provider. Jentic generates and maintains this spec from the Azure Resource Manager contracts so that AI agents and developers can call Microsoft Storage Sync via structured tooling. It is validated against the live API and kept up to date. Get started with Jentic One, the self-hosted execution layer.

What authentication does the Microsoft Storage Sync API use?

The API uses Azure Active Directory OAuth 2.0 with the user_impersonation scope against https://login.microsoftonline.com/common/oauth2/authorize. Jentic stores the Azure AD client secret or service principal credentials encrypted in its vault; agents receive scoped bearer tokens at execution time and never see the underlying credential.

Can I register a new on-premises file server with the Microsoft Storage Sync API?

Yes. Use PUT /subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.StorageSync/storageSyncServices/{storageSyncServiceName}/registeredServers/{serverId} to enroll a server. The server agent must already be installed on the host and must present a registration certificate, which the API validates before completing registration.

What are the rate limits for the Microsoft Storage Sync API?

Microsoft Storage Sync follows the standard Azure Resource Manager throttling limits, which apply per subscription and per region. Most management operations are limited to 1200 reads and 600 writes per hour per subscription. Long-running operations such as sync group provisioning return 202 Accepted and should be polled via the workflows endpoint rather than retried aggressively.

How do I create a sync group through Jentic?

Search Jentic for create azure storage sync group, then load the schema for PUT under storageSyncServices/{name}/syncGroups/{syncGroupName}. Execute the call with subscriptionId, resourceGroupName, storageSyncServiceName, and syncGroupName populated. Jentic handles the OAuth token exchange and returns the provisioned sync group identifier.

Does the Microsoft Storage Sync API handle cloud tiering policy?

Yes. Cloud tiering is configured on the server endpoint resource. When you create or patch a server endpoint, set cloudTiering to true and supply volumeFreeSpacePercent and tierFilesOlderThanDays to control which files are offloaded to the Azure file share.

Can I limit what my agent is allowed to do with the Microsoft Storage Sync API?

Yes. Jentic One is self-hosted, so your own rules decide which operations and credentials the agent may use. Because the subscription, resource group, Storage Sync Service name, and server id all live in the URL path, you can pin the agent to a single Storage Sync Service so it can register servers and create sync groups under that service and nothing else. You choose exactly which operations it may call, so destructive ones like deleting a registered server or a sync group stay off the list unless you explicitly add them.

GET STARTED

Start building with Microsoft Storage Sync API

Explore with Jentic One
View OpenAPI Document