Azure DevOps / Overview / Wiki / Trusted Publisher System / Partner Resources / First time Onboarding / 4.
First time Onboarding / 4. Create your licensing co Sea
GitHub Copilot is available for all BAP developers. Read the guidelines and sign up at aka.ms/github/copilot.
OneCRM
aka.ms/github/copilot
4. Create your …
Overview
OneCRM.wiki Matthew Leonard Aug 1, 2023
Summary
Enter page title
Dashboards
Contents
• About
Wiki
• Free or Paid?
• User or Resource license type
Boards
• The TPS license data model
• Free apps
Repos
• What happens at first time provisioning
Table Type Support
• Notable limitations
Pipelines
TPS Portal Registration • Tenant home geo
Test Plans Trusted Publisher System
Artifacts Releases, HotFix steps an… About
Before you can sell to a customer, you must associate your
Partner Resources
Compliance application with one or more service plans. These service plans
exist outside of TPS and are a prerequisite to creation of TPS
First time Onboarding
license information.
Portfolio++
About applications, …
Start Right
Free or Paid?
1. Onboard to Partn…
At this point in onboarding, you have an important decision to
IDC-TeDC 2. Publish your offer… make. Should your application require a subscription?
3. Onboard to the T… TPS supports two licensing flows.
OneBranch
4. Create your licen… 1. Paid - The application will only be visible to customers who
have a license
Bundles 2. Free - The application is always available
RequiresLicense fl… If Paid, then the application requires one or more bundles; each
bundle links to a single entitlement and one or more applications.
Preview licensing
If Free, then the application will show up in PPAC automatically.
Example of creati… No Entitlements or Bundles are required.
Important! The default license type is Paid. If your app should be
5. Publish to Test re… free to all users, you will have to request a change in TPS as
outlined here
6. Publish to produc…
Manage your applicati… User or Resource license type
A second important decision is User versus Resource license type.
Troubleshooting
User licenses are per seat
Tps ACIS Guide
Resource license types are per environment
Telemetry
Important! This is a permanent decision and cannot be changed
TSGs once you create an entitlement.
AppMgmt Internal The TPS license data model
TSG for issue 383109280: D…
UCI Field Controls
UCI Grid Control
UCI Visualizations This data model describes how TPS manages licenses for paid
applications
Unified Routing
Subscribed Plans are pulled in from the Neptune Licensing
User Management Service (which syncs with Commerce)
Subscribed Plans = Service Plans = SKU
Utility to Populate Task, Ema…
Tenant Subscription Plans represent the subscribed plans
Wiki Template for Readiness that have been pulled into Neptune for a given user.
Entitlements hold onto the capability string (also called
Project settings New page entitlement code) within Neptune and thus allow a mapping
b t th hi h li i t
