Before you begin, I know that this is a common problem, as it can be seen from this post, but please bear with me.

I have a potentially circular use of foreign keys, can someone help me understand my problem and provide a potential fix for this problem?

BlogPost and Comment are my entities, where the user can comment on blog posts, and the blog post id is added to each comment on create, as well as user id.

public partial class BlogPost
{
  public string Title { get; set; }
  public string? Text { get; set; }
  public int UserId { get; set; }
  // Navigation Properties
  public virtual User User { get; set; }
  public virtual ICollection<Comment> Comments { get; set; }
}

public partial class Comment
{
    public string Text { get; set; }
    public int? UserId { get; set; }
    public int? BlogPostId { get; set; }
    // Navigation Properties
    public virtual User User { get; set; }
    public virtual BlogPost BlogPost { get; set; }
}

This are my Configurations for each entity

public void Configure(EntityTypeBuilder<Comment> builder)
{
  builder.HasKey(t => t.Id);
  builder.HasOne(d => d.User)
      .WithMany(p => p.Comments)
      .HasForeignKey(t => t.UserId)
      .OnDelete(DeleteBehavior.Cascade);

  builder.HasOne(d => d.BlogPost)
      .WithMany(p => p.Comments)
      .HasForeignKey(t => t.BlogPostId)
      .OnDelete(DeleteBehavior.Cascade);
}
public void Configure(EntityTypeBuilder<BlogPost> builder)
{
  builder.Property(t => t.Title).HasMaxLength(60).IsRequired();
}

This is the error that I get when trying to apply migrations:

Introducing FOREIGN KEY constraint ‘FK_Comments_BlogPosts_BlogPostId’ on table ‘BlogPosts’ may cause cycles or multiple cascade paths. Specify ON DELETE NO ACTION or ON UPDATE NO ACTION, or modify other FOREIGN KEY constraints. Could not create constraint or index. See previous errors.

Please let me know if you need further informations.