new role assignment azure

Manage Azure Role Assignments Like a Pro with PowerShell

Today’s blog post is a little bit different. I have a couple of examples of how you can use PowerShell snippets and simple commandlets to get or set role assignmnets in your Azure Subscriptions.

PowerShell examples for managing Azure Role assignments

List all role assignments in a subscription, get all role assignments for a specific resource group, get all role assignments for a specific user, add a role assignment to a user, remove a role assignment for a user, remove all role assignments for a specific user, list all built-in roles, list all custom roles, create a custom role, update a custom role, delete a custom role, list all users or groups assigned to a specific role, list all permissions granted by a specific role, list all resource groups that a user has access to, create a role assignment for a service principal, powershell script to manage azure role assignments.

And now there is a script that combines some of these examples into one usable function:

I hope this was useful. Let me know if you liked the format of this blog and if you want me to include more of these examples.

Vukasin Terzic

Recent Update

• Writing your first Azure Terraform Configuration
• Transition from ARM Templates to Terraform with AI
• Getting started with Terraform for Azure
• Terraform Configuration Essentials: File Types, State Management, and Provider Selection
• Dynamically Managing Azure NSG Rules with PowerShell

Trending Tags

Retrieve azure resource group cost with powershell api.

The Future Of Azure Governance: Trends and Predictions

Further Reading

In my previous blog posts, I wrote about how simple PowerShell scripts can help speed up daily tasks for Azure administrators, and how you can convert them to your own API. One of these tasks is...

Azure Cost Optimization: 30 Ways to Save Money and Increase Efficiency

As organizations continue to migrate their applications and workloads to the cloud, managing and controlling cloud costs has become an increasingly critical issue. While Azure provides a robust s...

Custom PowerShell API for Azure Naming Policy

To continue our PowerShell API series, we have another example of a highly useful API that you can integrate into your environment. Choosing names for Azure resources can be a challenging task. ...

New-AzRoleAssignment

In this Azure PowerShell article, we will discuss the syntax and usage of the New-AzRoleAssignment Azure PowerShell cmdlet with examples.

Table of Contents

Wrapping Up

New-AzRoleAssignment is a very good PowerShell command that you can use to assign an RBAC role to a specific principal for a specified scope. Let’s discuss the Syntax of the New-AzRoleAssignment Azure PowerShell cmdlet.

Below is the syntax of the New-AzRoleAssignment PowerShell command.

Now, let’s discuss some examples of how to use the New-AzRoleAssignment PowerShell command.

You can execute the below Azure PowerShell command to grant a contributor role to the user “[email protected]” under the resource group “MyNewResGrp” scope, and the role assignment is available for delegation.

Below Azure PowerShell cmdlet can help you to grant owner access to the user “[email protected]” to the “TsInfoweb” website.

You may also like following the articles below

• Get-AzRoleAssignment
• Get-AzRoleDefinition

In this Azure PowerShell article, we discussed the syntax and usage of the New-AzRoleAssignment Azure PowerShell cmdlet with examples. Thanks for reading this article !!!

I am Rajkishore, and I have over 14 years of experience in Microsoft Azure and AWS, with good experience in Azure Functions, Storage, Virtual Machine, Logic Apps, PowerShell Commands, CLI Commands, Machine Learning, AI, Azure Cognitive Services, DevOps, etc. Not only that, I do have good real-time experience in designing and developing cloud-native data integrations on Azure or AWS, etc. I hope you will learn from these practical Azure tutorials. Read more .

• Adding or removing role assignments using Azure Portal

Go back to AZ-304 Tutorials

In this article you will learn about assigning roles using Azure portal and the process of adding and removing role assignments. 

However, Azure’s role-based access control (RBAC) refers to the authorization system for managing access to Azure resources. And, to grant access, you assign roles to users, groups, service principals, or managed identities at a particular scope. 

Prerequisites

For adding or removing role assignments, you must have:

• Firstly, Microsoft.Authorization/roleAssignments/write 
• Secondly, Microsoft.Authorization/roleAssignments/delete permissions, such as User Access Administrator or Owner

Access control (IAM)

Access control (IAM) is the page that is for assigning roles to grant access to Azure resources. It’s also known as identity and access management and appears in several locations in the Azure portal. There are questions for assigning roles to help in understanding about the Access control (IAM) page.

• Who needs access? This refers to a user, group, service principal, or managed identity. 
• What role do they need? Permissions are grouped together into roles, so you can select from a list of several built-in roles orcan use custom roles.
• Where do they need access? This refers to the set of resources that the access applies to. However, “where” can be a management group, subscription, resource group, or a single resource such as a storage account.

Adding a role assignment

• Firstly, in the Azure portal, click All services and then select the scope that you want to grant access to. 
• Secondly, click the specific resource for that scope.
• Then, Click Access control (IAM).
• Fourthly, click the Role assignments tab for viewing the role assignments at this scope.
• After that, click Add > Add role assignment. However, if you don’t have permissions to assign roles, the Add role assignment option will be disabled.

• Then, in the Role drop-down list, select a role such as Virtual Machine Contributor.
• There in the Select list, select a user, group, service principal, or managed identity. And, if you don’t see the security principal in the list, you can type in the Select box to search the directory for display names, email addresses, and object identifiers.
• Lastly, click Save to assign the role.

Assigning a user as an administrator of a subscription

For giving users the role of an administrator of an Azure subscription, first assign them the Owner role at the subscription scope. As the Owner role gives the user full access to all resources in the subscription, including the permission to grant access to others. However, these steps are the same as any other role assignment.

• Firstly, in the Azure portal, click All services and then Subscriptions.
• Then, click the subscription where you want to grant access.
• Thirdly, click Access control (IAM).
• After that, click the Role assignments tab to view the role assignments for this subscription.
• Then, click Add > Add role assignment. However, if you don’t have permissions to assign roles, the Add role assignment option will be disabled.
• And, in the Role drop-down list, select the Owner role.
• Then, in the Select list, select a user.

Adding a role assignment for a managed identity

For adding role assignments for a managed identity use the Access control (IAM) page. However, when you use the Access control (IAM) page, you start with the scope and then select the managed identity and role. In this section, you will learn about an alternate way to add role assignments for a managed identity. Using these steps, you start with the managed identity and then select the scope and role.

System-assigned managed identity

• Use these steps for assigning a role to a system-assigned managed identity by starting with the managed identity.
• Firstly, in the Azure portal, open a system-assigned managed identity. Then, in the left menu, click Identity.

• After that, under Permissions, click Azure role assignments. However, if roles are already assigned to the selected system-assigned managed identity then you will see the list of role assignments.
• For changing the subscription, click the Subscription list. Then, click Add role assignment.
• Then, use the drop-down lists to select the set of resources that the role assignment applies to such as Subscription, Resource group, or resource. And, if you don’t have role assignment write permissions for the selected scope, an inline message will be displayed.
• After that, in the Role drop-down list, select a role such as Virtual Machine Contributor.

User-assigned managed identity

• Use these steps for assigning a role to a user-assigned managed identity by starting with the managed identity.
• Firstly, in the Azure portal, open a user-assigned managed identity. Then, in the left menu, click Identity.
• After that, under Permissions, click Azure role assignments. However, if roles are already assigned to the selected user-assigned managed identity then you will see the list of role assignments.

Removing a role assignment

In Azure RBAC, for removing access from an Azure resource, you first remove a role assignment. Use these steps to remove a role assignment.

• Firstly, Open Access control (IAM) at a scope, such as management group, subscription, resource group, or resource, where you want to remove access.
• Then, click the Role assignments tab to view all the role assignments for this subscription.
• After that, in the list of role assignments, add a checkmark next to the security principal with the role assignment you want to remove.
• Then, Click Remove.
• Lastly, in the remove role assignment message that appears, click Yes.

However, if you see a message that inherited role assignments cannot be removed, then you are trying to remove a role assignment at a child scope. So, you should open Access control (IAM) at the scope where the role was assigned and try again. 

Reference: Microsoft Documentation

Prepare for Assured Success

Stefanos Cloud

How to manage Microsoft 365 user role assignments and administrative units

• Role assignments
• Administrative Units

This article provides guidance on how to manage Microsoft 365 user role assignments and administrative units. The article is also available on my podcast and Youtube channel .

View this article as a how-to video on Youtube.

You need to manage existing user roles, create new custom user roles and assign users and groups to existing roles in Microsoft 365 . You need to also manage Microsoft 365 administrative units.

In this how-to article, we will show you how to manage Microsoft 365 user role assignments and administrative units.

Role assignments #

From within the Microsoft 365 Admin Center portal, you can assign ‎ Azure AD‎ built-in roles to users who need access to other admin centers and resources in ‎ Azure Active Directory‎, such as users, groups, and apps which use ‎Microsoft Graph‎ API. The following groups of user role assignments can be made from the Admin Center portal.

• Azure AD role assignments
• Exchange Online role assignments
• Intune role assignments

In the next steps, we will show you how to assign the Global Administrator Azure AD role to a user and group. Follow the steps below to assign the Global Administrator role to a user or group.

• Navigate to https://admin.microsoft.com and authenticate as a global admin user.
• On the left pane, expand the "Roles" section and click on "Role assignments". On the main section click on the "Global Administrator" role. On the popup form on the right, you should be able to review the general properties of the role in question. On the permissions tab, the system lists details of the permissions which are assigned with the role in question.
• On the "Assigned" tab, you can assign users or groups to the role in question. Click on "Add Users" and then "Add Groups" to add a user and group respectively to the specific role.
• To run the Azure portal as a specific Azure AD user role, tick on the checkbox next to the role and click "Run As". This will show you the view of the Azure portal as if you had logged in via a user with the role in question.
• To compare permissions of user roles, tick on two or more roles and then click on "Compare Roles". In the next screen, you should see a tabular comparison of the permissions assigned to each of the compared roles. You can also click on "Export comparison" to export the comparison matrix of the selected roles.

In the next steps, we will show you how to assign the Organization Management Exchange Online role to a user and group, as well as how to create a new custom Exchange Online role. Follow the steps below.

• Navigate to the "Exchange" tab under the "Role Assignments" section.
• Click on the "Organization Management" role. On the popup form on the right, you can review the general settings of the role under the "general" tab. Under the "Permissions" tab, you can review in detail the available permissions of the role in question.
• Under the "Assigned" tab, you can assign a user or group to the role in question. Click "Add" and choose the user or group to assign to the role.
• You can also create a custom Exchange Online role by ticking the checkbox next to the role which will be used as the template for the new role. Then click on "Copy role group". This will take you to a wizard to create your new custom role. On the "Set up the basics" page, fill-in the name, description and write scope of the new role and click Next.
• Select the roles to add to the ‎new custom role group. Roles define the scope of the tasks that the members assigned to this role group have permission to manage.
• Select the users to assign to this role group. They'll have permissions to manage the roles that you assigned in the previous step.
• Review your selections and click Finish.

In the next steps, we will show you how to assign Intune roles. Assign ‎Intune‎ roles to specialists who need to view or manage ‎Intune‎ data, devices, or services. These roles can only be assigned to users who have a license that includes ‎Intune‎. Follow the steps below.

• Under the "Role assignments" section, navigate to the "Intune" tab. If you need to export existing assignments, click on the "Export assignments" button.
• Click on the Intune role you wish to edit assignments of. On the "General tab" you can review the general settings of the role in question. On the "Permissions" tab you can see in detail all permissions of the role in question.
• To assign users to the Intune role, under the "Assigned" tab click on "Add". This will take you to the "Set up the basics" wizard. Fill-in a name and description and click Next.
• Select the security groups that contain the users you want to become admins for the role. Click Next.
• Select a built-in security group like 'All users', or search for and select security groups which contain the users and devices that the ‎Intune role can manage.
• You can optionally add tabs which limit the specific Intune policies, apps and devices that the admins can see. Click "Next".
• Review all your assignment settings and click "Finish".

Administrative Units #

Now we will move on to show you how to create and manage Microsoft 365 Administrative Units. Units let you sub-divide your organization into any unit that you want, and then assign specific administrators that can only manage that unit. For example, you can assign the Helpdesk Administrator role to a regional support specialist, so they can manage users only in that region.

Carry out the following steps:

• Under the "Roles" section, click on "Administrative Units". Click on "Add Unit" to add a new administrative unit.
• Provide a name and Description of the new administrative unit and click "Next". Administrative units let you limit admins to manage users for a specific department, region, or any segment that your organization defines. Start by giving the administrative unit a name and description that will let other admins know its purpose.
• Choose "Add up to 20 users and groups" or "Upload users" if you need to bulk upload a large number of users to be linked to the new administrative unit. If you choose "Add up to 20 users and groups", then click on "Add Users" or "Add Groups" to add the desired users to the administrative unit and click Next. The administrators assigned to this unit will manage the settings for these users and groups. Adding groups doesn't add users to the unit, it lets the assigned admins manage group settings. You can only add up to ‎20‎ members individually or you can bulk upload up to ‎200‎ users. If you need to add more, you can edit this unit to add them.
• Assign admins to scoped roles. The following roles are the only roles that support administrative units. Authentication Administrator Cloud Device Administrator Groups Administrator Helpdesk Administrator License Administrator Password Administrator SharePoint Administrator Teams Administrator Teams Device Administrator User Administrator.

Select a role and then assign admins to it. The admins that you assign to roles in this step will manage the members of this administrative unit.

• Review your selections and click "Finish". The new administrative unit has been created. You can always edit its properties by clicking on the Administrative Unit name. From that page you can edit the administrative unit's members and role assignments.
• You can also edit the name and description of an administrative unit by ticking the checkbox next to the administrative unit name and clicking on "Edit name and description".

What are your Feelings

Share this article :, how can we help.

Powered by BetterDocs

This browser is no longer supported.

Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.

Assign Azure roles using Azure Resource Manager templates

• 13 contributors

Azure role-based access control (Azure RBAC) is the authorization system you use to manage access to Azure resources. To grant access, you assign roles to users, groups, service principals, or managed identities at a particular scope. In addition to using Azure PowerShell or the Azure CLI, you can assign roles using Azure Resource Manager templates . Templates can be helpful if you need to deploy resources consistently and repeatedly. This article describes how to assign roles using templates.

Bicep is a new language for defining your Azure resources. It has a simpler authoring experience than JSON, along with other features that help improve the quality of your infrastructure as code. We recommend that anyone new to infrastructure as code on Azure use Bicep instead of JSON.

To learn about how to define role assignments by using Bicep, see Create Azure RBAC resources by using Bicep . For a quickstart example, see Quickstart: Assign an Azure role using Bicep .

Prerequisites

To assign Azure roles, you must have:

• Microsoft.Authorization/roleAssignments/write permissions, such as Role Based Access Control Administrator or User Access Administrator

You must use the following versions:

• 2018-09-01-preview or later to assign an Azure role to a new service principal
• 2020-04-01-preview or later to assign an Azure role at resource scope
• 2022-04-01 is the first stable version

For more information, see API versions of Azure RBAC REST APIs .

Get object IDs

To assign a role, you need to specify the ID of the user, group, or application you want to assign the role to. The ID has the format: 11111111-1111-1111-1111-111111111111 . You can get the ID using the Azure portal, Azure PowerShell, or Azure CLI.

To get the ID of a user, you can use the Get-AzADUser or az ad user show commands.

To get the ID of a group, you can use the Get-AzADGroup or az ad group show commands.

Managed identities

To get the ID of a managed identity, you can use Get-AzAdServiceprincipal or az ad sp commands.

Application

To get the ID of a service principal (identity used by an application), you can use the Get-AzADServicePrincipal or az ad sp list commands. For a service principal, use the object ID and not the application ID.

Assign an Azure role

In Azure RBAC, to grant access, you assign a role.

Resource group scope (without parameters)

The following template shows a basic way to assign a role. Some values are specified within the template. The following template demonstrates:

• How to assign the Reader role to a user, group, or application at a resource group scope

To use the template, you must do the following:

• Create a new JSON file and copy the template
• Replace <your-principal-id> with the ID of a user, group, managed identity, or application to assign the role to

Here are example New-AzResourceGroupDeployment and az deployment group create commands for how to start the deployment in a resource group named ExampleGroup.

The following shows an example of the Reader role assignment to a user for a resource group after deploying the template.

Resource group or subscription scope

The previous template isn't very flexible. The following template uses parameters and can be used at different scopes. The following template demonstrates:

• How to assign a role to a user, group, or application at either a resource group or subscription scope
• How to specify the Owner, Contributor, and Reader roles as a parameter

To use the template, you must specify the following inputs:

• The ID of a user, group, managed identity, or application to assign the role to
• A unique ID that will be used for the role assignment, or you can use the default ID

This template is not idempotent unless the same roleNameGuid value is provided as a parameter for each deployment of the template. If no roleNameGuid is provided, by default a new GUID is generated on each deployment and subsequent deployments will fail with a Conflict: RoleAssignmentExists error.

The scope of the role assignment is determined from the level of the deployment. Here are example New-AzResourceGroupDeployment and az deployment group create commands for how to start the deployment at a resource group scope.

Here are example New-AzDeployment and az deployment sub create commands for how to start the deployment at a subscription scope and specify the location.

Resource scope

If you need to assign a role at the level of a resource, set the scope property on the role assignment to the name of the resource.

The following template demonstrates:

• How to create a new storage account
• How to assign a role to a user, group, or application at the storage account scope

To deploy the previous template, you use the resource group commands. Here are example New-AzResourceGroupDeployment and az deployment group create commands for how to start the deployment at a resource scope.

The following shows an example of the Contributor role assignment to a user for a storage account after deploying the template.

New service principal

If you create a new service principal and immediately try to assign a role to that service principal, that role assignment can fail in some cases. For example, if you create a new managed identity and then try to assign a role to that service principal in the same Azure Resource Manager template, the role assignment might fail. The reason for this failure is likely a replication delay. The service principal is created in one region; however, the role assignment might occur in a different region that hasn't replicated the service principal yet.

To address this scenario, you should set the principalType property to ServicePrincipal when creating the role assignment. You must also set the apiVersion of the role assignment to 2018-09-01-preview or later. 2022-04-01 is the first stable version.

• How to create a new managed identity service principal
• How to specify the principalType
• How to assign the Contributor role to that service principal at a resource group scope
• The base name of the managed identity, or you can use the default string

Here are example New-AzResourceGroupDeployment and az deployment group create commands for how to start the deployment at a resource group scope.

The following shows an example of the Contributor role assignment to a new managed identity service principal after deploying the template.

• Quickstart: Create and deploy ARM templates by using the Azure portal
• Understand the structure and syntax of ARM templates
• Create resource groups and resources at the subscription level
• Azure Quickstart Templates

Coming soon: Throughout 2024 we will be phasing out GitHub Issues as the feedback mechanism for content and replacing it with a new feedback system. For more information see: https://aka.ms/ContentUserFeedback .

Submit and view feedback for

Additional resources

• Max Scherzer Ahead Of Schedule, Could Return In Early May
• Rangers Promote Jack Leiter
• Robert Stephenson To Miss 2024 Season With Elbow Injury
• Astros To Activate Justin Verlander On Friday
• Whitey Herzog Passes Away
• Dodgers To Promote Andy Pages
• Hoops Rumors
• Pro Football Rumors
• Pro Hockey Rumors

MLB Trade Rumors

Blue Jays Designate Mitch White For Assignment

By Darragh McDonald | April 16, 2024 at 3:20pm CDT

The Blue Jays announced today that right-handers Jordan Romano and Erik Swanson have been activated off the injured list. In corresponding moves, they optioned righty Nate Pearson to Triple-A and designated righty Mitch White for assignment.

Romano and Swanson were key pieces of the Toronto bullpen last year but they haven’t been able to contribute to the club thus far in 2024. During the spring, Romano had some inflammation in his elbow while Swanson had some tightness in his forearm, leading both to start the season on the injured list.

With those two unavailable, the club has turned to Yimi García and Chad Green for most of the high-leverage work, with those two filling in admirably. García has a 1.17 earned run average through seven appearances, with 11 strikeouts to go with just one walk. Green, meanwhile, has a 2.35 ERA in his seven appearances, with seven punchies and two walks.

Despite that strong work from those two, the Jays are surely glad to get Romano and Swanson back. Romano has emerged as the club’s closer over the past three years, which included saving 36 games in each of the past two campaigns while keeping his ERA under 3.00 in each. Swanson had 29 holds and four saves last year while posting a 2.97 ERA on the season. Those two, along with García and Green, give the Jays a strong four-headed bullpen mix to finish out games.

The health of that group has nudged White off the roster. Now 29, White was a second-round pick of the Dodgers back in 2016 and was considered by Baseball America to be the #69 prospect in the league in 2018. The Jays acquired him in a 2022 deadline deal alongside Alex De Jesus , with prospects Nick Frasso and Moises Brito going the other way.

At the time of that deal, White had thrown 105 2/3 big league innings with a 3.58 ERA, 22% strikeout rate and 8.3% walk rate. Unfortunately, the jersey swap corresponded with an immediate downturn in his results. White tossed 43 innings for the Jays in 2022 with a 7.74 ERA and 15.3% strikeout rate. There was a bit of bad luck in there, as his .368 batting average on balls in play and 54.3% strand rate were both on the unfortunate side, which is why his FIP was 3.76 in that time and his SIERA 4.70.

Luck or not, the poor results meant the Jays couldn’t guarantee a rotation spot to White going into 2023. At that time, four rotation spots were taken by Alek Manoah , Kevin Gausman , José Berríos and Chris Bassitt . White went into Spring Training battling Yusei Kikuchi for the final spot but dealt with some shoulder and elbow injuries and had to start the season on the IL. By the time he got back, there was no rotation spot for him and he worked a long relief role in the bullpen.

He didn’t take to that move, posting a 7.11 ERA in 10 outings before being designated for assignment. The 29 other clubs passed on the chance to grab him off waivers and he was sent outright to Triple-A. He got stretched out in Buffalo and finished the season in good form, with a 1.89 ERA over his last 33 1/3 innings, pairing a 31.4% strikeout rate in that time with a 10.2% walk rate.

The Jays added him back to the 40-man in November to prevent him from reaching minor league free agency, which put him in a similar spot to where he was a year prior, coming into spring out of options and battling for a spot. The Jays had to put Manoah on the IL this spring, which opened a rotation spot, but Bowden Francis beat White for that gig. Now that Yariel Rodríguez has also been stretched out and has seemingly bumped Francis from the rotation, White has been moved even further back. He has only made four long relief appearances this year but his uninspiring 5.40 ERA in those surely didn’t help him.

White has now been bumped off the roster yet again and the Jays will have one week to work out a trade or pass him through waivers. Since he cleared waivers last year, doing so again would give him the right to elect free agency. It’s possible he may garner interest based on his past results and strong finish at Triple-A last year. The fact that he’s out of options means that he needs an active roster spot somewhere, but he has less than three years of service time, meaning he can be controlled for three more seasons beyond this one.

A number of teams around the league are dealing with significant pitching injuries and it was less than a week ago that the Jays managed to flip Wes Parsons to the Guardians for international bonus pool space. Parsons is optionable but is more than two years older than White and doesn’t have the same past prospect pedigree.

36 Comments

I guess maybe a team like the A’s or Marlins could put in a claim for white, but I assume he’ll remain in the jays system

Name correlates well to the story about Mitch White.

White is another overrated prospect from LAD, even the A’s should take a pass on him.

I got to hand it to LAD they surely make out when trading these overhyped prospects and getting good return so far Frasso may have higher upside in the end.

Although they have lost out with Busch but they had no where to place him.

Like they did with Yordan Alvarez

White was a lot better with LA than Toronto. I wonder why…

Why the hell would they option Pearson. He’s been nothing short of outstanding. The guy is finally putting it together and they ship him back to AAA

It’s called options. He’ll be back as soon as another injury happens

All other right handers in their pen have looked good, only the two lefties look horrible but they probably don’t want to go with just one lefty in the pen

6.1 innings of awesome after years of not so awesome. Who would you have lost out of the bullpen instead?

Two Jays starters aren’t fully stretched out. They need a long man in the bullpen. Pearson is not it.

Damn the curse of having options for Pearson.

I recommended the Jays release Mitch White in Aug 2022 when he was acquired because with the BlueJays he is not a MLB level pitcher. What a waste of time and money. Let Mitch White go for good.

The Mitch White deal reminds me of trading star in the making Moreno for Varsho, which was also called a bad deal at that time too.

Pearson belongs in the bigs. He’ll be back. If they use him as a one inning guy Pearson can be a very good pitcher. Pearson needs a one inning per use managed and reduced workload to maintain performance excellence.

Atkins is bad, no one denies it.

Get creative and trade excess 2b to AA , for something we need like a good bat for the of Got clement ikf Biggio Schneider… atl could use a bat at 2b w Albies out for a while

Finally ,another atkins mistake dfa’d . Shakin’ My Head …..

Hasn’t been all bad with Atkins on the pitching side. Brought in guys like Matz Robbie ray stripling Kikuchi etc and got the most out of them. They let em go and they stink or hurt. Good call to go to Gausman instead of ray for the dough . Got Romano Jimmy Garcia for nothing as afterthoughts Built good pens last few years. It’s the offence he’s bad , both drafting and at the mlb level.

And where has that got us ??

They were in on Ray as well. He wanted too much though

Im not a shatkins guy and doo want them both gon but you can deny that have made great decisions alomost with all there signing and every trade but 2. Even the trad for Grichuk for example sure he never lived up to want they hoped but thay nothing for him. Drafting bad or very inconveniently draft good player is this jays groups down fall

@Murphy NFLD

The Grichuks trade wasn’t all that good. The 5 year, 50M deal was nothing short of awful.

This is a premature move. With Gausman not Gausman’ing, Rodriguez having less than 5 IP of pro ball (no innings pitched last year at any league level) and Kikuchi pitching more than 5 innings only 10 times since the start of ’23, the Jays needed someone to give them innings. Even comparing Francis to White, the numbers are similar, but Francis has an option.

To put this in perspective, if the FO options Francis instead, then a week later a starter hits the IL, Francis can come back up to fill the spot. With this decision, Francis fills the spot and who becomes the long man?

Just poor roster management.

Perhaps they felt like it would not be beneficial for Bowden Francis to go down despite his numbers right now. Mitch White hasn’t had a good track record in the majors for quite some time.

I think they should trade Mitch White (if they can) for more international international signing bonus money…

The need is to chuck in a guy to cover Rodriguez, Gausman, and maybe Kikuchi. Francis can come in for one of them for multiple innings. Richards can take one of the remaining 2. After that, you’re looking at leveraged arms coming in non leveraged spots. DFA’ing White was a move that was coming but it shouldn’t have been this early. In tennis terms, this is an unforced error.

I have a feeling that they’ll be able to nab a similar arm off waivers in short order.

I agree with this. I’m not comfortable about the innings that need covering. I’d have optioned Francis and kept White. Jays fans hate White. But there are a few things he does well enough and a number 6 or 7 starter isn’t really going to perform like a 3 or 4. Does he perform well enough compared to other depth starters? I think there’s reason to think he can. But I also think Rodriguez looks like he can leave the game with the team in good shape and Francis seems to do a lot better in that shorter stint bridge to the leverage arms role than White and they are probably projecting a very tight race for those wild card spots and playing for the games immediately in front of them more than having the luxury of thinking about the longer term and preserving depth. With the benefit of hindsight, I would have just DFA’d White instead of Parsons at the time. Then with this move they could have just optioned Peason and Parsons and the active roster would look the same with a full 40 man roster that still had Parsons available as depth. But they just signed this year’s version of Parsons in Mike Mayers, so maybe they see traits there they think they can tap into.

Too bad about Pearson but this made some sense. Neither LH bullpen arm is going anywhere, they need Bowden to eat innings, and the rest firmly have a place in the bullpen.

They could have gotten creative by sending Francis down and putting White in his spot in the rotation. Would he have been worse? I’d argue that, based on Francis’ early season numbers, White may have been slightly better. But probably not enough to warrant such a move. Also, I don’t know if Francis has options left. If not, the Blue Jays probably value him much more than they do White.

@Baseball77

Francis has one option left.

White is better than nobody. His presence has been unnecessary since the horrendous trade happened.

What specific factors led to Mitch White’s designation for assignment, considering his past prospect pedigree and recent strong finish at Triple-A, and how does this decision align with the Blue Jays’ long-term pitching strategy?

I suspect the decision was made by throwing darts at the wall or playing beer pong. Applying logic, reason, or common sense fails.

The long term pitching strategy is the interesting part of the question. I find it surprising that they DFA’d Parsons who still had an option only to turn around and DFA White a couple weeks later. They didn’t need the 40 man spot. Only the active one. Moving on from both Parsons and White when Rodriguez isn’t expected to be a big source of innings and Francis lost his his starting gig for now seems like a move you make when you are confident you have someone claiming a stake to a depth role. I’m not sure who that is. The prospects in AAA are having a rough transition so they aren’t particularly close and the veteran AAA arms are less inspiring than White or Parsons. Manoah is a very big part of the conversation but also a very big mystery. In terms of the long term, they don’t seem to have a lot of guys who fit into the traditional starter mold. What they do have is kind of hybridized guys who can move fast up the system. Most of them will back down to single inning types but I wonder if they might be comfortable with the idea they can be more competitive with bullpen games featuring multi inning types than throwing out lousy depth starters .

Management basically looked at the roster of pitchers and said to themselves ״who’s the worst “ came up with Mitch.

The white flag has been dfa’d

At this point, White is a quadruple-A player. Good enough to be fill in for an injury, but not good enough to stick. Out of options means he’ll be on the dfa carousel and shuttling among the many mlb franchises if he’s lucky. Otherwise, it’s Asia, Mexico, or some other line of work….

“Meanwhile” can’t come in the middle of a sentence, MLBTR. It has to START the sentence.

Leave a Reply Cancel reply

Please login to leave a reply.

Log in Register

• Feeds by Team
• Commenting Policy
• Privacy Policy

MLB Trade Rumors is not affiliated with Major League Baseball, MLB or MLB.com

Username or Email Address

Remember Me

Search code, repositories, users, issues, pull requests...

Provide feedback.

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly.

To see all available qualifiers, see our documentation .

• Notifications