pyaz/synapse/role/assignment/__init__.py
def delete(workspace_name, assignee=None, assignee_object_id=None, ids=None, item=None, item_type=None, role=None, scope=None, yes=None):
    '''
    Delete role assignments of workspace.

    Required Parameters:
    - workspace_name -- The workspace name.

    Optional Parameters:
    - assignee -- Represent a user or service principal. Supported format: object id, user sign-in name, or service principal name.
    - assignee_object_id -- Use this parameter instead of '--assignee' to bypass Graph API invocation in case of insufficient privileges. This parameter only works with object ids for users, groups, service principals, and managed identities. For managed identities use the principal id. For service principals, use the object id and not the app id.
    - ids -- space-separated role assignment ids. You should not provide --role or --assignee when --ids is provided.
    - item -- Item granted access in the workspace. Using with --item-type to combine the scope of assignment.Using az role assignment with filter condition before executing delete operation to be clearly aware of which assignments will be deleted.
    - item_type -- Item type granted access in the workspace. Using with --item to combine the scope of assignment.Using az role assignment with filter condition before executing delete operation to be clearly aware of which assignments will be deleted.
    - role -- The role name/id that is assigned to the principal.
    - scope -- A scope defines the resources or artifacts that the access applies to. Synapse supports hierarchical scopes. Permissions granted at a higher-level scope are inherited by objects at a lower level. In Synapse RBAC, the top-level scope is a workspace. Using az role assignment with filter condition before executing delete operation to be clearly aware of which assignments will be deleted.
    - yes -- Do not prompt for confirmation.
    '''
    return _call_az("az synapse role assignment delete", locals())

    Delete role assignments of workspace.

    Required Parameters:
    - workspace_name -- The workspace name.

    Optional Parameters:
    - assignee -- Represent a user or service principal. Supported format: object id, user sign-in name, or service principal name.
    - assignee_object_id -- Use this parameter instead of '--assignee' to bypass Graph API invocation in case of insufficient privileges. This parameter only works with object ids for users, groups, service principals, and managed identities. For managed identities use the principal id. For service principals, use the object id and not the app id.
    - ids -- space-separated role assignment ids. You should not provide --role or --assignee when --ids is provided.
    - item -- Item granted access in the workspace. Using with --item-type to combine the scope of assignment.Using az role assignment with filter condition before executing delete operation to be clearly aware of which assignments will be deleted.
    - item_type -- Item type granted access in the workspace. Using with --item to combine the scope of assignment.Using az role assignment with filter condition before executing delete operation to be clearly aware of which assignments will be deleted.
    - role -- The role name/id that is assigned to the principal.
    - scope -- A scope defines the resources or artifacts that the access applies to. Synapse supports hierarchical scopes. Permissions granted at a higher-level scope are inherited by objects at a lower level. In Synapse RBAC, the top-level scope is a workspace. Using az role assignment with filter condition before executing delete operation to be clearly aware of which assignments will be deleted.
    - yes -- Do not prompt for confirmation.
    
Delete role assignments of workspace.
Required Parameters:
workspace_name -- The workspace name.

Optional Parameters:
assignee -- Represent a user or service principal. Supported format: object id, user sign-in name, or service principal name.
assignee_object_id -- Use this parameter instead of '--assignee' to bypass Graph API invocation in case of insufficient privileges. This parameter only works with object ids for users, groups, service principals, and managed identities. For managed identities use the principal id. For service principals, use the object id and not the app id.
ids -- space-separated role assignment ids.
Delete role assignments of workspace . Required Parameters : workspace_name -- The workspace name . Optional Parameters : assignee -- Represent a user or service principal . Supported format : object id user sign - in name or service principal name . assignee_object_id -- Use this parameter instead of ' -- assignee ' to bypass Graph API invocation in case of insufficient privileges . This parameter only works with object ids for users groups service principals and managed identities . For managed identities use the principal id . For service principals use the object id and not the app id . ids -- space - separated role assignment ids .
def delete(workspace_name, assignee=None, assignee_object_id=None, ids=None, item=None, item_type=None, role=None, scope=None, yes=None):
    return _call_az("az synapse role assignment delete", locals())
def delete ( workspace_name , assignee = None , assignee_object_id = None , ids = None , item = None , item_type = None , role = None , scope = None , yes = None ) : return _call_az ( "az synapse role assignment delete" , locals ( ) )
Delete role assignments of workspace.
Delete role assignments of workspace .
'''
    Delete role assignments of workspace.

    Required Parameters:
    - workspace_name -- The workspace name.

    Optional Parameters:
    - assignee -- Represent a user or service principal. Supported format: object id, user sign-in name, or service principal name.
    - assignee_object_id -- Use this parameter instead of '--assignee' to bypass Graph API invocation in case of insufficient privileges. This parameter only works with object ids for users, groups, service principals, and managed identities. For managed identities use the principal id. For service principals, use the object id and not the app id.
    - ids -- space-separated role assignment ids. You should not provide --role or --assignee when --ids is provided.
    - item -- Item granted access in the workspace. Using with --item-type to combine the scope of assignment.Using az role assignment with filter condition before executing delete operation to be clearly aware of which assignments will be deleted.
    - item_type -- Item type granted access in the workspace. Using with --item to combine the scope of assignment.Using az role assignment with filter condition before executing delete operation to be clearly aware of which assignments will be deleted.
    - role -- The role name/id that is assigned to the principal.
    - scope -- A scope defines the resources or artifacts that the access applies to. Synapse supports hierarchical scopes. Permissions granted at a higher-level scope are inherited by objects at a lower level. In Synapse RBAC, the top-level scope is a workspace. Using az role assignment with filter condition before executing delete operation to be clearly aware of which assignments will be deleted.
    - yes -- Do not prompt for confirmation.
    '''
workspace_name
assignee
assignee_object_id
ids
item
item_type
role
scope
yes