Custom Metadata

Custom Metadata lets you add your own business fields to the inventory, cost centers, project codes, classifications, anything Microsoft does not track, then use those fields the same way you use any built-in property: to scope a Policy, group a Report, fill in a Provisioning form, or set a value from an Automation.

Custom Metadata is included in the Enterprise Plan and available as an add-on to the Premium Plan.

What You Can Define

• Custom properties: A typed field you add to an existing inventory object, for example a Cost Center field on Teams. Choose from five data types: Text, Number, Date, Single select, and Yes-No.
• Custom objects: A new inventory of your own, for example a list of cost centers or SAP project codes, with its own property schema and its own instances.
• Custom relations: A link from an object to exactly one instance of another object, for example a Team to its Cost Center, created separately from a Custom Property. The link is visible on both ends.
• Data sources: A SharePoint file or library that keeps a Custom Object or a property’s values current automatically, refreshed at least every four hours or on demand.

Where You Will Find It

Every customization you create, on any service, is listed on one page, Manage your metadata. From there you add, edit, or remove a Custom Property, Relation, Object, or data source, and control whether a property is shown to end users in the Teams App.

Beyond the inventory itself, Custom Metadata shows up across Rencore Governance:

• In Policies and Reports, as a filter, a group-by field, or an exclusion rule that keeps Automations off objects you mark as protected.
• In Provisioning, as fields on the request form, so business context is captured when a workspace is created instead of chased down later.
• In reviews, as a step where the workspace owner fills in or corrects a property.
• In Automation, through the Set a custom property value action, which writes a value when a lifecycle event happens.